Closed erwamartin closed 2 months ago
Note: I downgraded the destination connector to version 2.6.1 (my previous version) and it's working fine.
This is normal. To ensure the connector works properly, you must update both the connector and platform versions when new features are released. Closing as the error message give direction of what is needed to fix the problem.
This is normal. To ensure the connector works properly, you must update both the connector and platform versions when new features are released. Closing as the error message give direction of what is needed to fix the problem.
@marcosmarxm I'm sorry but I don't understand. My AirByte version is already set to 0.63.1
, so why does this message appear?
Same happening with Airbyte Platform version 0.63.2 and destination-bigquery connector version 2.8.0.
@marcosmarxm could you please re-open this issue?
@erwamartin my bad!!! I totally lose the platform version. I'll ask the engineering team to take a look
Same happening with Airbyte Platform version 0.63.2 and destination-bigquery connector version 2.8.0.
What source and connector version you're using?
Hello @erwamartin, Could you help me to understand the sequence of events here? I am wondering who got updated first, did you bump the platform version before bumping the connector version or the opposite?
Thanks,
@erwamartin could you run the following query on the airbyte DB? And let me know the result.
SELECT supports_refreshes
FROM public.actor_definition_version
where docker_repository = 'airbyte/destination-bigquery' and docker_image_tag = '2.7.1';
Hi @benmoriceau, thank you for your answers!
Hello @erwamartin, Could you help me to understand the sequence of events here? I am wondering who got updated first, did you bump the platform version before bumping the connector version or the opposite?
Thanks,
I may have updated the connector first, and then the platform.
@erwamartin could you run the following query on the airbyte DB? And let me know the result.
SELECT supports_refreshes FROM public.actor_definition_version where docker_repository = 'airbyte/destination-bigquery' and docker_image_tag = '2.7.1';
Here is the output (I downgraded the destination connector to version 2.6.1):
airbyte=# SELECT supports_refreshes FROM public.actor_definition_version where docker_repository = 'airbyte/destination-bigquery' and docker_image_tag = '2.7.1';
supports_refreshes
--------------------
f
(1 row)
Thanks, @erwamartin this is confirming the theory I had about the sequence of events which lead to this issue. I am preparing a fix and I will update the ticket when a new version of the platform which is fixing this is released.
Hello @erwamartin, The implementation of the fix is taking a little bit more than expected. We would like to avoid doing a hack and switch to a more long term solution. Our plan is to re-import the actor definition when starting the airbyte platform. It would have set the right value in the definition table after you upgraded the airbyte platform.
In the meantime, could you run the following query. It will allow you to upgrade to the latest version of big query (or 2.7.1).
UPDATE public.actor_definition_version
SET supports_refreshes=true
WHERE docker_repository = 'airbyte/destination-bigquery' AND (docker_image_tag IN ('2.7.0', '2.7.1', '2.8.0', '2.8.1'));
Let me know if that works for you.
Hi @benmoriceau, I just ran the SQL update query, and upgraded the bigquery connector. It worked fine š Thank you for your help! š
Great, I will close the ticket.
Connector Name
destination-bigquery
Connector Version
2.7.1
What step the error happened?
During the sync
Relevant information
I'm getting the following error while syncing Intercom to Bigquery:
AirByte version is 0.63.1.
Relevant log output
Contribute