You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "nsivabalan (via GitHub)" <gi...@apache.org> on 2026/06/25 02:02:39 UTC
Re: [I] Refactor the configure framework of hudi project [hudi]
nsivabalan commented on issue #14510:
URL: https://github.com/apache/hudi/issues/14510#issuecomment-4795177616
Triage: this looks resolved on `master`. The configuration framework requested here has been implemented:
- `org.apache.hudi.common.config.ConfigProperty<T>` binds the key, default value, deprecated keys, docs, and type-safe inference into a single class — addressing the first bullet ("config item and default value may defined in a class").
- `ConfigClassProperty` / `ConfigGroups` annotations group configs by component, and configs have been split out of the fat `HoodieWriteConfig` into per-component classes (`HoodieMetricsConfig`, `HoodieAWSConfig`, `HoodieIndexingConfig`, `HoodieStorageConfig`, `HoodieMemoryConfig`, `HiveSyncConfig`, `BigQuerySyncConfig`, `KafkaConnectConfigs`, etc.) — addressing the second bullet ("extract some config items for specific component").
The core refactor landed in commit d412fb2fe642 (`[HUDI-89] Add configOption & refactor all configs based on that`, #2833) and has been built on extensively since. If there is a more specific gap not covered by the current framework, it would be helpful to file a focused issue describing it; otherwise this can likely be closed.
--
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: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org