voonhous opened a new issue, #19996: URL: https://github.com/apache/hudi/issues/19996
Follow-up to #18780 (RFC-105 hudi-trino migration), blocking trinodb/trino#30682. ### What Trino's Hudi connector has a `hudi.max-split-size` config property (maximum size of a single split, default `120MB`). It was added in trinodb/trino#29866, shipped in Trino 483, and is documented in the Trino Hudi connector docs. `HudiConfig` in `hudi-trino` does not have this property. It has `hudi.target-split-size` (default `128MB`, also exposed as the `target_split_size` session property) instead. Once trinodb/trino#30682 switches the Trino Hudi plugin to `hudi-trino`, any catalog that sets `hudi.max-split-size` fails to start with an unused configuration property error. Catalogs that leave it unset quietly move from a 120MB to a 128MB split size. ### Proposed fix - Accept `hudi.max-split-size` in `hudi-trino`'s `HudiConfig`, for example as a `@LegacyConfig` alias of `hudi.target-split-size`, so existing catalogs keep working. - Decide which default to keep (120MB or 128MB) and note the change in the release notes if it differs from Trino 483. - Update `TestHudiConfig` to cover the alias. ### Why here Under RFC-105, `HudiConfig` lives in `org.apache.hudi:hudi-trino`, so the Trino-side plugin can no longer add or alias config properties itself. -- 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]
