lw309637554 commented on pull request #2136: URL: https://github.com/apache/hudi/pull/2136#issuecomment-743769396
> > option 1: check GLOBAL_BLOOM incompatible with BLOOM strict. It will be concise > > yes. but that takes the flexibilty away. I have seen users start with global bloom and then move to bloom, for perf reasons for eg. > > actually. option 2, seems like the right thing to me. but I can see that it's heavy weight. Ideally, hoodie.properties is a hudi file group, that can take updates or is versioned as well. that's also a large change. > > So, I am actually bit puzzled. :| Let me think more. > if you have any other way out of this, please let me know as well . @vinothchandar thanks , i think we can do as option2. just like AbstractUpgradeDowngrade update the properties. but at index persist scenario, we can retain the old properties endwith the version of timestamp ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
