Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back 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.
Not sure what this patch is fixing for, shouldn't the
buildSyncConfig
already take care of this config option ?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.
buildSyncConfig() just put config into
HiveSyncContext.props
, but notHiveSyncConfig.hadoopConf
. When running to constructor of HMSDDLExecutor, it callsyncConfig.getHiveConf()
to use theHiveSyncConfig.hadoopConf
:this.client = Hive.get(syncConfig.getHiveConf()).getMSC();
There is no code to put 'hive_sync.metastore.uris' from
HiveSyncContext.props
tosyncConfig.getHiveConf()
. Which make an exception when use hive sync by metastore.I found the code is removed in the pull: https://github.com/apache/hudi/pull/5854 . I think it causes the error.
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.
Maybe this is not a good place to put the code, so it is removed in the pr-5854. But it is effective after adding the code back.
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 confirmation, it is a valid fix though ~