-
Notifications
You must be signed in to change notification settings - Fork 319
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
[#1253] bugfix(jdbc): fix jdbc catalog store empty audit info issue #1257
Conversation
3ed9e35
to
c8c2aad
Compare
Will this pull request back port to branch 0.3? |
I have added a label |
@qqqttt123 please help to review. |
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.
LGTM, thanks @jerryshao @Clearvive
@@ -276,7 +276,7 @@ public Table loadTable(NameIdentifier tableIdent) throws NoSuchTableException { | |||
} | |||
Map<String, String> properties = | |||
load.properties() == null ? Maps.newHashMap() : Maps.newHashMap(load.properties()); | |||
StringIdentifier.addToProperties(id, properties); | |||
properties = StringIdentifier.addToProperties(id, properties); |
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.
Could you rename addToProperties
to a more proper name?
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.
ok, added.
…1257) ### What changes were proposed in this pull request? Mysql&Postgres catalog store empty audit info fix. ### Why are the changes needed? Fix: #1253 ### Does this PR introduce _any_ user-facing change? Users will receive audit information ### How was this patch tested? IT --------- Co-authored-by: Clearvive <clearvive@datastrato.com>
What changes were proposed in this pull request?
Mysql&Postgres catalog store empty audit info fix.
Why are the changes needed?
Fix: #1253
Does this PR introduce any user-facing change?
Users will receive audit information
How was this patch tested?
IT