-
Notifications
You must be signed in to change notification settings - Fork 1k
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
chore: add key_schema_id and value_schema_id to format properties #8185
Conversation
ee9d01b
to
7f12e81
Compare
b2bfafb
to
beff574
Compare
1589b56
to
bd0b22d
Compare
e8e8eee
to
c6558bc
Compare
d12257b
to
72ea4a3
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.
One nit. Overall LGTM.
As discussed in person, we should update the PR title, because moving the properties is not the main objective of the PR, but adding the schema-ids to the JSON is.
@@ -299,7 +311,12 @@ private void compare( | |||
) { | |||
final Object expected = extractStatement.apply(statement, config); | |||
final Object actual = extractSource.apply(dataSource); | |||
if (!actual.equals(expected)) { | |||
|
|||
if (actual == null && expected == null) { |
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.
Do we need this check? IIRC Objects.equals(null,null)
is a valid call and it will return true
?
Nice catch on the NPE issue though!
Description
This PR depends on #8177. Review after this commit: c760b58.
key_schema_id
andvalue_schema_id
toCommonCreateConfig
since the property will be used byC*AS
as well asCREATE WITH
command later.schema_id
property in format properties so that it can be used to choose translation policy (i.e. uppercase field name or not uppercase them) see refactor: Refactor ConnectFormatSchemaTranslator to take translator object instead of lamda function so that the translator can take in config to decide how to transform field names #8177, chore: add options to control field name case in schema translation #8213.*schema_id
to YATT test.Test done