deepakpanda93 commented on issue #16625: URL: https://github.com/apache/hudi/issues/16625#issuecomment-5189629393
This issue was reviewed as part of the JIRA-migrated backlog triage. Findings: no documentation change is outstanding here — the behaviour this ticket asked us to document was already documented before the fix landed. `website/docs/hoodie_streaming_ingestion.md` on the `asf-site` branch covers table-level configuration for `HoodieMultiTableStreamer` in its "MultiTableStreamer" section: - `--config-folder` — "the path to the folder which contains all the table wise config files" - `hoodie.streamer.ingestion.tablesToBeIngested` - `hoodie.streamer.ingestion.<database>.<table>.configFile` — "path to the config file in dedicated config folder which contains table overridden properties for the particular table to be ingested" - plus a pointer to the sample per-table configs under `hudi-utilities/src/test/resources/streamer-config` That text is byte-identical to the version at `asf-site` commit `08032842fbf1` (2024-07-27) — two months *before* HUDI-7711 (`4bbb8dac20e1`, PR #11149, merged 2024-09-21), which changed only `HoodieMultiTableStreamer.java`, one test class and three test `.properties` fixtures, and no documentation. In other words the docs were already accurate and the implementation was corrected to match them, so the gap this ticket describes closed from the code side rather than the docs side. The only edits to that section since are cosmetic: the `HoodieStreamer` → `Hudi Streamer` rename, a modernised `spark-submit` example, and a link to the multi-table ingestion blog post. If you were expecting something more specific — a worked per-table example, or an explicit callout of the pre-HUDI-7711 broken behaviour for users on older versions. please reopen and say which, and we'll scope it separately. Closing as already addressed. -- 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]
