[
https://issues.apache.org/jira/browse/SOLR-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599239#comment-16599239
]
Christine Poerschke commented on SOLR-12697:
--------------------------------------------
bq. ... I have supported both numeric values representations (Point* and
Trie*). ...
Ah, sorry, I missed that detail, thanks for drawing my attention to that.
(Haven't yet taken a closer look at this part of your changes.)
bq. ... And I'm not sure, do I need to create a patch for Solr 6? The attached
patch will work for Solr 7 and 8.
Fair question. Development usually happens on the {{master}} git branch and
then typically (but not always) is backported to the major release branch
(currently {{branch_7x}}). The prior branches e.g. {{branch_6x}} would receive
(selected) bug fixes only.
https://lucene.apache.org/solr/community#about-versions has some more info. So
in short, if the patch works for Solr 7 and 8 that's great and there is no need
for a patch for Solr 6 for this performance optimisation/new feature change.
> pure DocValues support for FieldValueFeature
> --------------------------------------------
>
> Key: SOLR-12697
> URL: https://issues.apache.org/jira/browse/SOLR-12697
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - LTR
> Reporter: Stanislav Livotov
> Priority: Major
> Attachments: SOLR-12697.patch
>
>
> [~slivotov] wrote in SOLR-12688:
> bq. ... FieldValueFeature doesn't support pure DocValues fields (Stored
> false). Please also note that for fields which are both stored and DocValues
> it is working not optimal because it is extracting just one field from the
> stored document. DocValues are obviously faster for such usecases. ...
> (Please see SOLR-12688 description for overall context and analysis results.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
