deepakpanda93 commented on issue #17068:
URL: https://github.com/apache/hudi/issues/17068#issuecomment-5393975215

   This is done - closing, with a note on which PR did it, since there are two 
linked here and only one merged.
   
   **#19650 is the one that closed this.** It merged to `asf-site` on 
2026-08-24 and its description opens with
   "Closes #17068. (JIRA: HUDI-9550.)"
   
   Checking the published page rather than relying on the merge, all four items 
from the description are now live in
   `website/learn/tech-specs.md`:
   
   | item | where |
   |---|---|
   | internal `indexVersion` field | `:500-501` - *"`version` holds a 
`HoodieIndexVersion`, an index-level attribute introduced in table version 9"* |
   | new SI partition scheme | `:592-594`, `:605` - delimiter and escaping 
rules, keyed off `HoodieIndexVersion` |
   | null value handling | `:594` (null character escaping), `:423` |
   | upgrade/downgrade dropping indexes | `:521` *"Table Upgrade and 
Downgrade"*, `:532` *"Dropped indexes have to be rebuilt after the downgrade."* 
|
   
   Worth recording one thing that came out of writing it: the page did not just 
omit the V2 partition scheme, it
   described it **backwards** - stating that V2 shards by primary key and makes 
secondary-key range scans worse, when
   `MetadataPartitionType#getFileGroupMappingFunction` and
   `HoodieTableMetadataUtil#getSecondaryKeyToFileGroupMappingFunction` show the 
opposite. That correction is the more
   valuable half of the change.
   
   Since it merged to `asf-site` it is already published rather than waiting on 
a release.
   
   **#13713 still needs its own decision** - it is broader than this ticket 
("Index related doc update for hudi 1.1"),
   so closing this issue should not be taken as retiring that PR.
   
   Closing.


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

Reply via email to