[
https://issues.apache.org/jira/browse/HUDI-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903457#comment-17903457
]
Y Ethan Guo commented on HUDI-8429:
-----------------------------------
User still needs to "register" the custom merger implementation added by the
user so the Hudi knows which merger classes to look up based on the merge
strategy UUID. The problem to be solved here is for the user to be able to
query the table without providing an extra config of merge implementation class
(which should be added in the table config), by simply adding the jar
containing the merger implementation class.
> Persist record merging implementation classes to table config
> -------------------------------------------------------------
>
> Key: HUDI-8429
> URL: https://issues.apache.org/jira/browse/HUDI-8429
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Y Ethan Guo
> Priority: Critical
> Labels: needs-attention
> Fix For: 1.0.1
>
>
> For CUSTOM merge mode, the list of record merging implementation classes is
> required for the record merging to work. Persisting it to the table config
> makes it easier for query engines to know which one to use, without passing
> additional config.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
