lokeshj1703 opened a new pull request, #8152:
URL: https://github.com/apache/hudi/pull/8152

   ### Change Logs
   
   The configs in the following classes are implemented not using HoodieConfig, 
making it impossible to be surfaced on the Configurations page.  We need to 
refactor the code so that each config property is implemented using 
ConfigProperty in a corresponding new HoodieConfig class.  Refer to 
HoodieArchivalConfig for existing implementation of configs.
   
   InitialCheckPointProvider
   HoodieDeltaStreamer
   HoodieMultiTableDeltaStreamer
   FilebasedSchemaProvider
   HiveSchemaProvider
   JdbcbasedSchemaProvider
   ProtoClassBasedSchemaProvider
   SchemaPostProcessor
   SchemaRegistryProvider
   SparkAvroPostProcessor
   DropColumnSchemaPostProcessor
   BaseSchemaPostProcessorConfig
   
   KafkaOffsetPostProcessor
   
   SanitizationUtils
   
   Also 'hoodie.deltastreamer.multiwriter.source.checkpoint.id' in 
HoodieWriteConfig
   
   ### Impact
   
   NA
   
   ### 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_
   
   - _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