-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 CDK] Fix java interop compilation issue in Config/TransientErrorException. #41996
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
I only reviewed the exception constructor stuff, one nit in the changelog + a nonblocking suggestion
...rbyte-cdk/dependencies/src/main/kotlin/io/airbyte/commons/exceptions/ConfigErrorException.kt
Outdated
Show resolved
Hide resolved
Do we know why this regression was not caught by any of the tests done by CI when we merged the last one? |
...ces/src/main/kotlin/io/airbyte/cdk/integrations/debezium/internals/DebeziumRecordIterator.kt
Outdated
Show resolved
Hide resolved
Possibly related to #41999 |
@@ -213,6 +213,11 @@ public void close() throws Exception { | |||
} | |||
} | |||
|
|||
@Override | |||
public Optional<AirbyteStreamNameNamespacePair> getAirbyteStream() { |
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.
What is the problem/ticket resulting from the lack of this implementation?
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.
The default implementation of getAirbyteStream()
is to return Optional.empty()
so each iterator that implements the AirbyteStreamAware
interface needs to implement this method.
I noticed this during testing that we were throwing a NoSuchElementException instead of the relevant TransientException
Mentioned this in the standup - connector tests are run only if the CDK version is togged. Likely for that PR only the relevant (destination) tests were run so this wasn't caught |
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.
Looks good, let's split into different smaller PRs next time (as they are addressing issues that are orthogonal) :-)
@@ -213,6 +213,11 @@ public void close() throws Exception { | |||
} | |||
} | |||
|
|||
@Override | |||
public Optional<AirbyteStreamNameNamespacePair> getAirbyteStream() { |
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.
Is a similar change required on other connectors?
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.
Yes. That will have been reflected in the PRs associated with WASS changes in the relevant connectors
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.
Note that due to #41647 DebeziumRecordIterator.isHeartbeatEvent() is currently broken.
Not sure if limited to a driver or a version.
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.
Yeah this PR wont help that case. Then again it won't handle or make anything worse.
/publish-java-cdk
|
Fixes a compilation issue in the construction of transient & config errors which was a minor regression introduced in a previous PR due to issues with Kotlin/Java interop