waitingF opened a new issue, #10348: URL: https://github.com/apache/hudi/issues/10348
**_Tips before filing an issue_** - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)? - Join the mailing list to engage in conversations and get faster support at [email protected]. - If you have triaged this as a bug, then file an [issue](https://issues.apache.org/jira/projects/HUDI/issues) directly. **Describe the problem you faced** The issue I encountered is: Ingest the data with hudi 0.14.1 as MERGE_ON_READ, I want to decode the log file to debug via hudi-cli. But the hudi-cli version was 0.12.1, it throws the error IndexOutOfBound at below code in org.apache.hudi.common.table.log.block.HoodieLogBlock#getLogMetadata ```java public enum HeaderMetadataType { INSTANT_TIME, TARGET_INSTANT_TIME, SCHEMA, COMMAND_BLOCK_TYPE, COMPACTED_BLOCK_TIMES, RECORD_POSITIONS, BLOCK_IDENTIFIER, IS_PARTIAL } // getLogMetadata method metadata.put(HeaderMetadataType.values()[metadataEntryIndex], new String(metadataEntry)); ``` As new enums added since 0.12.1, so exception throws when decode those new enums here. Currently for LogBlockHeader `HeaderMetadataType` types, forward compatibility has been achieved by adding new enums at the end. Do we need to maintain backward compatibility? **To Reproduce** Steps to reproduce the behavior: 1. ingest into MOR with hudi version 0.14.1 2. decode the log file via hudi-cli version 0.12.1 **Expected behavior** low version hudi-cli can decode those high version log file, but ignore those new enums. **Environment Description** * Hudi version : * Spark version : * Hive version : * Hadoop version : * Storage (HDFS/S3/GCS..) : * Running on Docker? (yes/no) : **Additional context** Add any other context about the problem here. **Stacktrace** ```Add the stacktrace of the error.``` -- 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]
