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

Posted to issues@lucene.apache.org by "Jason Gerlowski (Jira)" <ji...@apache.org> on 2019/11/11 20:55:00 UTC

[jira] [Assigned] (LUCENE-9026) Make it easier to extend DocValuesTermsQuery

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

Jason Gerlowski reassigned LUCENE-9026:
---------------------------------------

    Assignee: Jason Gerlowski

> Make it easier to extend DocValuesTermsQuery
> --------------------------------------------
>
>                 Key: LUCENE-9026
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9026
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>    Affects Versions: master (9.0)
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Minor
>         Attachments: LUCENESOLR-9026.patch
>
>
> The visibility of some of the fields in DocValuesTermsQuery make it difficult to efficiently subclass.  Especially the "termData" instance variable, which is really core to the functioning of the class but is totally inaccessible from any sub-classes, forcing subclasses to store a duplicate PrefixCodedTerms object, and then juggle the state of both.
> Are there any objections to making "termData" (and potentiall some other instance variables) protected instead of private for this class?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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