chrevanthreddy commented on PR #20107: URL: https://github.com/apache/hudi/pull/20107#issuecomment-6448261785
Compatibility question before we retain any vector-specific freshness machinery: @cvinoth, is the release/table format carrying the vector index intended to require a table-version bump that fences older writers? Current master routes configured/inflight metadata partition paths through MetadataPartitionType.fromPartitionPath, which rejects unknown vector_index_* paths, so an older writer that observes the partition fails closed. We have not yet established the behavior of a pre-existing writer with cached pre-index table configuration. We want to reuse Hudi RLI/SI compatibility semantics rather than add a per-commit frontier for a writer that is already fenced. Could you confirm the intended writer compatibility/table-version contract? -- 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]
