You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "nsivabalan (via GitHub)" <gi...@apache.org> on 2026/06/25 03:06:39 UTC

Re: [I] Ensure new fileId format is good across all code paths and backwards compatible [hudi]

nsivabalan commented on issue #15637:
URL: https://github.com/apache/hudi/issues/15637#issuecomment-4795458305

   This appears to be addressed in current master. `HoodieTableMetadataUtil.getFileIdLengthWithoutFileIndex` (hudi-common/src/main/java/org/apache/hudi/metadata/HoodieTableMetadataUtil.java:2366-2368) handles both formats — `files-0000` (legacy) and `files-0000-0` (new) — by checking for the `-0` suffix and stripping it when present. The downstream helpers `getFileGroupIndexFromFileId` and `getFileGroupPrefix` rely on this rather than on a hardcoded character length, so callers don't depend on exact char length. Tests covering both formats: `TestHoodieBackedMetadata.java:3629-3631` and `TestJavaHoodieBackedMetadata.java:2497-2499`. The handling was introduced in commit 7ae8da02d126 (HUDI-6200). Safe to close — please reopen if there are specific code paths that still assume one format only.


-- 
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