linliu-code opened a new pull request, #12801:
URL: https://github.com/apache/hudi/pull/12801

   ### Change Logs
   
   We expect precombine as mandatory config to be set for mutable streams. For 
immutable streams, precombine could be avoided based on the writer. With 
HoodieStreamer, for immutable streams, we could set precombine as empty string 
and get a pipeline running. This just works bcoz, the precombine is never used 
anywhere (compaction, snapshot read, dedup etc). But if user enables 
"filterDupes" feature with HoodieStreamer, it breaks.
   
   So, in this patch we are relaxing the constraint. Users can still avoid 
setting precombine and enable "filterDupes" feature with HoodieStreamer. Not 
only for immutable streams, for mutable streams it should be feasible to use 
"OverwriteWithLatestAvroPayload" and get an end to end stream working w/o a 
need to set an explicit ordering field.
   
   So, this patch takes a stab at enabling this.
   
   ### Impact
   
   Fix a corner case.
   
   ### Risk level (write none, low medium or high below)
   
   Low.
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change. If not, put "none"._
   
   - _The config description must be updated if new configs are added or the 
default value of the configs are changed_
   - _Any new feature or user-facing change requires updating the Hudi website. 
Please create a Jira ticket, attach the
     ticket number here and follow the 
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to