Re: [I] New file format does not work with in memory index [hudi]

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

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

   This issue appears to be obsolete. The linked PR #10062 was closed without merging in October 2024. Subsequently, commit `2ebc6775` (PR #14060, *refactor(spark): Remove glob paths and deprecate read paths support*, Nov 2025) removed glob paths support entirely:
   
   - `HoodieInMemoryFileIndex.scala` was deleted
   - `DefaultSource.createRelation` now throws `HoodieException("Glob paths are not supported for read paths as of Hudi 1.2.0")` when a glob/read-paths option is detected
   
   The original failure mode — "file index empty when using `IndexType.INMEMORY`, so we need to fall back to glob paths" — is therefore no longer reachable in master. `HoodieInMemoryHashIndex` (the writer-side INMEMORY index) still exists and works through the standard read path on the new file format.
   
   If the underlying scenario (querying with `IndexType.INMEMORY`) still misbehaves on master with a non-glob path, please reopen with a concrete repro. Otherwise this can be closed as obsolete.


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