Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destination BigQuery Denormalized : workaround for #14023 #15363

Closed
DoNotPanicUA opened this issue Aug 5, 2022 · 0 comments · Fixed by #14023
Closed

Destination BigQuery Denormalized : workaround for #14023 #15363

DoNotPanicUA opened this issue Aug 5, 2022 · 0 comments · Fixed by #14023
Assignees
Labels
needs-triage type/enhancement New feature or request

Comments

@DoNotPanicUA
Copy link
Contributor

Tell us about the problem you're trying to solve

Right now, we cannot release a version without backward compatibility. Such change can affect existing cloud users and their production connections.
To improve our current version handling for such cases, we designed improvements for the Airbyte. But they are blocked till new metadata handling for the cloud is still under development.
Until then, we should handle both implementations inside connectors to avoid affecting existing users. (This strategy is confirmed by @grishick)

Describe the solution you’d like

#14023 (comment)
For PR #14023 we need to implement the old and new versions of the processing and use the proper one for existing connections (with old schema) and for all others (which can use new).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage type/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant