Mrart opened a new issue, #8653: URL: https://github.com/apache/paimon/issues/8653
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version paimon 1.1.1 +flink 1.18 Basically, all the trigger conditions are met: 1. DEBUG logging was enabled for org.apache.paimon.flink.lookup.FileStoreLookupFunction in the production environment. 2. A lookup join is being used, and the table created is a SecondaryIndexLookupTable. 3. The join key is contract_no, which is not the complete primary key. The logs show _KEY_contract_no and _KEY_reg_valid, indicating that the full key also involves reg_valid. 4. There is a mismatch in the field order among the lookup projection, Paimon's internal read schema, and the original table schema. 5. The DEBUG branch attempts to print the matched rows, which leads to the execution of logRow(). LookupJoin[8] switched from RUNNING to FAILED java.lang.RuntimeException: java.lang.IndexOutOfBoundsException at org.apache.paimon.flink.lookup.FileStoreLookupFunction.lookup ... Caused by: java.lang.IndexOutOfBoundsException at org.apache.paimon.memory.MemorySegment.get at org.apache.paimon.memory.MemorySegmentUtils.copyToBytes at org.apache.paimon.data.BinaryString.toString at org.apache.paimon.flink.lookup.FileStoreLookupFunction.logRow at org.apache.paimon.flink.lookup.FileStoreLookupFunction.lambda$lookupInternal$4 ### Compute Engine flink 1.18 ### Minimal reproduce step 1. DEBUG logging was enabled for org.apache.paimon.flink.lookup.FileStoreLookupFunction in the production environment. 2. A lookup join is being used, and the table created is a SecondaryIndexLookupTable. 3. The join key is contract_no, which is not the complete primary key. The logs show _KEY_contract_no and _KEY_reg_valid, indicating that the full key also involves reg_valid. 4. There is a mismatch in the field order among the lookup projection, Paimon's internal read schema, and the original table schema. 5. The DEBUG branch attempts to print the matched rows, which leads to the execution of logRow(). ### What doesn't meet your expectations? none ### Anything else? _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
