-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Java connectors use protocol v0 objects #20404
Java connectors use protocol v0 objects #20404
Conversation
/test connector=connectors/source-postgres
Build FailedTest summary info:
|
/test connector=connectors/source-postgres
Build FailedTest summary info:
|
@edgao, @akashkulk, while looking into the connector failure, found extra references to the v-null objects. |
/test connector=connectors/destination-snowflake
Build PassedTest summary info:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the heads up - not expecting anything to break here 🤞hopefully the tests pass
@gosusnp review is requested from the extensibility team but this doesn't seem to touch any extensibility code. Was that review request intentional? |
/test connector=connectors/source-postgres
Build PassedTest summary info:
|
Looks good - I assume that was why the Postgres test was failing? Just kicked off another run there |
@sherifnada, that was not intentional, I suspect some change detection script (Check if a review is required from Connector teams maybe?) automatically tagged extensibility |
/test connector=connectors/source-postgres
Build PassedTest summary info:
|
@akashkulk, I think b16f07d should fix the issues in the source-postgres. Just kicked off another run to confirm this. |
What
Migrate the Java connectors to use the protocol objects in the v0 namespace (
io.airbyte.protocol.models.v0
).Closes #20037
How
io.airbyte.protocol.models.v0
The object conversions is a short term mitigation for the build, a better solution should be implemented when we start migrating some connectors to the v1 of the protocol.
Recommended reading order
airbyte-protocol/protocol-models/src/main/java/io/airbyte/protocol/models/v0
contain the helper objects that have been duplicated to be version specificairbyte-integrations/bases/standard-source-test/src/main/java/io/airbyte/integrations/standardtest/source/AbstractSourceConnectorTest.java
,airbyte-integrations/bases/standard-destination-test/src/main/java/io/airbyte/integrations/standardtest/destination/DestinationAcceptanceTest.java
andairbyte-integrations/bases/standard-destination-test/src/main/java/io/airbyte/integrations/standardtest/destination/LocalAirbyteDestination.java
contain the tests that have been updated with the object conversionv0
objects rather than version-less objects.🚨 User Impact 🚨
There should be no behavior change, the
v0
andv1
of the protocol are structurally identical, what differs is the interpretation of some fields.