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

Posted to issues@lucene.apache.org by "Ignacio Vera (Jira)" <ji...@apache.org> on 2021/11/19 07:36:00 UTC

[jira] [Resolved] (LUCENE-9820) Separate logic for reading the BKD index from logic to intersecting it.

     [ https://issues.apache.org/jira/browse/LUCENE-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignacio Vera resolved LUCENE-9820.
----------------------------------
    Fix Version/s: 9.1
         Assignee: Ignacio Vera
       Resolution: Fixed

> Separate logic for reading the BKD index from logic to intersecting it.
> -----------------------------------------------------------------------
>
>                 Key: LUCENE-9820
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9820
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Ignacio Vera
>            Assignee: Ignacio Vera
>            Priority: Major
>             Fix For: 9.1
>
>          Time Spent: 10h 50m
>  Remaining Estimate: 0h
>
> Currently the class BKDReader contains all the logic for traversing the KD tree and the logic to read the actual index. This makes difficult to develop new visiting strategies, for example LUCENE-9619, where it is proposed to move Points from a visitor API to a custor-style API.
> The first step is to isolate the logic the read the index from the logic that visits the the tree. Another benefit of doing this, is that it will help evolving the index, for example moving the current index format to backwards codec without moving the visiting logic.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org