[jira] [Updated] (HUDI-4301) Detect HoodieMerge type with engine type automatically instead of the default avro-based one

[Vinoth Chandar (Jira)]

Title: Message Title

Vinoth Chandar updated an issue   Apache Hudi / HUDI-4301 Detect HoodieMerge type with engine type automatically instead of the default avro-based one Change By: Vinoth Chandar The same table be read by Spark or Hive for e.g I would love for such queries to be able to read and merge using the engine' POJO (Spark -> Row, Hive -> ArrayWritable), if the user chooses to write such a "merge" implementation.  For e.g consider this API {code:java} Option<HoodieRecord> combineAndGetUpdateValue(HoodieRecord older, HoodieRecord newer, Schema schema, Properties props) {   ... } {code} when writing from Spark we would use `HoodieSparkRecord` and the merge class would be `HoodieSparkMerge` in the table properties? and if we now read with Hive, it falls back to avro somehow?  Add Comment   This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)