lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (Jira)" <>
Subject [jira] [Commented] (LUCENE-9026) Make it easier to extend DocValuesTermsQuery
Date Mon, 04 Nov 2019 22:15:00 GMT


Mikhail Khludnev commented on LUCENE-9026:

{quote}I'm considering extending the query to implement Solr's [PostFilter|] interface.
The ultimate goal of this is to make it more efficient to run this query with very large numbers
of terms.
Hello, [~gerlowskija]. 

Please notice [method=docValuesTermsFilter|],
I suppose it's done it underneath.  

> Make it easier to extend DocValuesTermsQuery
> --------------------------------------------
>                 Key: LUCENE-9026
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>    Affects Versions: master (9.0)
>            Reporter: 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message