cshuo opened a new pull request, #19283: URL: https://github.com/apache/hudi/pull/19283
### Describe the issue this Pull Request addresses Lance tables were excluded from native log writing even when the effective write version supports native logs. This leaves Lance on the legacy inline-log path and prevents it from using the native log format consistently across write, compaction, CDC, and log-compaction flows. This PR enables native logs for Lance with write version TEN or later, and fixes log-file detection and reader format handling needed for native Lance log files. ### Summary and Changelog - Removes the Lance base-file-format exception from `CommonClientUtils.shouldWriteNativeLogs`, making write version the sole native-log gate. - Updates Spark, Flink, common write handles, CDC writers, and compaction paths to use the simplified native-log decision. - Adds explicit inline-log parsing through `FileNameParser.parseInlineLogFile` and makes `FSUtils.isInlineLogFile` distinguish inline logs from native logs and base files. - Updates Spark and Flink reader contexts so Lance native log files receive the correct format and vector-schema handling. ### Impact - **Functional impact**: Lance tables using write version TEN or later will write and read native log files instead of falling back to inline logs. - **Maintainability**: Centralizes the native-log eligibility rule around the effective write version and removes duplicated table-config dependencies. - **Extensibility**: Provides explicit inline-log recognition for readers that must distinguish inline and native log-file paths. ### Risk Level medium. The change affects MOR write, compaction, CDC, and reader paths across Spark and Flink. Unit coverage was updated for the native-log eligibility and inline-log detection rules. ### Documentation Update none. ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Enough context is provided in the sections above - [ ] Adequate tests were added if applicable -- 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]
