[I] Complex keygen encoding deduction can read a record another writer keyed [hudi]

["ad1happy2go (via GitHub)" <gi...@apache.org>]

ad1happy2go opened a new issue, #20202:
URL: https://github.com/apache/hudi/issues/20202

   Follows #19304. When \`hoodie.table.complex.keygenerator.encoding\` is missing, the writer deduces it from the first record of the first file the newest commit wrote. A commit that packs inserts into an existing small file (or clustering) rewrites the file with its older records first, keyed the way their writer keyed them, so on a table whose history spans the 0.14.0 and 0.14.1 key formats the deduction can return the older writer's encoding instead of the newest one's.
   
   Proposal: deduce from a record the newest commit wrote, i.e. the record with the greatest \`_hoodie_commit_time\` in a base file, and the data block that commit appended in a log file.


-- 
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: commits-unsubscribe@hudi.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Complex keygen encoding deduction can read a record another writer keyed [hudi]

["ad1happy2go (via GitHub)" <gi...@apache.org>]

ad1happy2go commented on issue #20202:
URL: https://github.com/apache/hudi/issues/20202#issuecomment-5994913565

   Fix in #20203.


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org