[ https://issues.apache.org/jira/browse/LUCENE-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402289#comment-17402289 ]
Michael Sokolov commented on LUCENE-10054: ------------------------------------------ Thanks for looking into this! could you expand *all* the abbreviations in the text below the diagram? EG I think "VDOffset" is "vector data offset"? I think it will help to clarify for readers. I wonder if we'll need {{ep}} as a special case -- it's really just the single node in the max level isn't it? Could you explain what is in each of the {{NodesLevelX}}? I guess it's a list of the ordinals in level 0 that are contained in the other level -- but I wonder if we will need this. Should we implement the in-memory version before defining the serialization? > Handle hierarchy in HNSW graph > ------------------------------ > > Key: LUCENE-10054 > URL: https://issues.apache.org/jira/browse/LUCENE-10054 > Project: Lucene - Core > Issue Type: Task > Reporter: Mayya Sharipova > Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently HNSW graph is represented as a single layer graph. > We would like to extend it to handle hierarchy as per > [discussion|https://issues.apache.org/jira/browse/LUCENE-9004?focusedCommentId=17393216&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17393216]. > > > TODO tasks: > - add multiple layers in the HnswGraph class > - modify the format in Lucene90HnswVectorsWriter and > Lucene90HnswVectorsReader to handle multiple layers > - modify graph construction and search algorithm to handle hierarchy > - run benchmarks -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org