You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Pratyaksh Sharma (Jira)" <ji...@apache.org> on 2019/11/08 07:00:00 UTC
[jira] [Issue Comment Deleted] (HUDI-114) Allow for clients to
overwrite the payload implementation in hoodie.properties
[ https://issues.apache.org/jira/browse/HUDI-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pratyaksh Sharma updated HUDI-114:
----------------------------------
Comment: was deleted
(was: [~nishith29] yeah I would like to have some more clarification before starting working on it. Precisely, I want to get more context on why one may need to pass new payload class name. It is already possible to configure it at run time using HoodieDeltaStreamer.Config class.
Also which is the datasource API you are talking about? )
> 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)