[
https://issues.apache.org/jira/browse/HUDI-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969936#comment-16969936
]
Pratyaksh Sharma commented on HUDI-114:
---------------------------------------
Hi [~nishith29], Here is how I plan to do it ->
When initialising DeltaSync, if suppose target base path already exists, I will
simply overwrite the payload name every time in hoodie.properties file with the
value passed by the user if the storage type is MERGE_ON_READ. Let me know if
this makes sense to you.
I went through the code, we store payload class name in hoodie.properties file
if the table type is MERGE_ON_READ. I have not gone through the entire flow for
MERGE_ON_READ table as of yet. It would be great if you could explain why do we
want to implement this functionality of overwriting the payload class. I am not
able to relate completely with this idea right now. With your valuable inputs,
I will be able to check if I am missing any scenario.
> Allow for clients to overwrite the payload implementation in hoodie.properties
> ------------------------------------------------------------------------------
>
> Key: HUDI-114
> URL: https://issues.apache.org/jira/browse/HUDI-114
> Project: Apache Hudi (incubating)
> Issue Type: Bug
> Components: newbie
> Reporter: Nishith Agarwal
> Assignee: Pratyaksh Sharma
> Priority: Minor
>
> Right now, once the payload class is set once in hoodie.properties, it cannot
> be changed. In some cases, if a code refactor is done and the jar updated,
> one may need to pass the new payload class name.
> Also, fix picking up the payload name for datasource API. By default
> HoodieAvroPayload is written whereas for datasource API default is
> OverwriteLatestAvroPayload
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
