-
Notifications
You must be signed in to change notification settings - Fork 164
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
[FLINK-36009] Architecture tests refactor #143
base: main
Are you sure you want to change the base?
Conversation
9e44d50
to
02c3783
Compare
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.
Hi, @eskabetxe Thank you for your hard work.
LGTM on the whole just the commit message header.
Would you mind helping update it ? thx~
fixed, the incorrect one was the PR that was using the Epic |
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 @eskabetxe for the update
LGTM +1 after merging & rebasing #144
@1996fanrui can you check |
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.
@1996fanrui can you check
This PR is related to Architecture refactor
, since I'm not an expert of jdbc-connector, so it's better to involve a commiter or PMC member related to connector, thanks.
cc @leonardBang
02c3783
to
99a0e50
Compare
@leonardBang @MartijnVisser can you help here.. |
import org.apache.flink.table.types.logical.RowType; | ||
|
||
/** JDBC converter for PostgreSQL compatible databases. */ | ||
@PublicEvolving | ||
@Internal |
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.
this is unclear to me
shouldn't we create a kind of FLIP first if we make such changes?
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.
This configuration is currently misaligned. All dialect implementations are classified as internal. The purpose of this class is solely to allow the CrateDB dialect to utilize the PostgreSQL implementation.
To preserve the PublicEvolving status, we need to add an exception to the architecture test. Without this exception, the rule "Public Evolving API Methods Use Only Public Evolving API Types" will fail.
To resolve this issue without an exception, we would need to refactor all dialect implementations and classify them as PublicEvolving.
I can add the exception if you still believe that a FLIP is necessary and focus the discussion solely on that change. I believe this will not impact the rest of the PR.
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 can add the exception if you still believe that a FLIP is necessary and focus the discussion solely on that change. I believe this will not impact the rest of the PR.
would be great.
Agree, rest of the PR is more or less ok (I did only a brief look, will look again a bit later)
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.
@snuyanzin already changed and added the exception to architecture tests.
When you have time could you check again..
Thanks
99a0e50
to
6d49ebe
Compare
Created the module flink-connector-jdbc-architecture to have all tests, we need to add the modules as dependency to validate that module..