You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Christine Poerschke (Jira)" <ji...@apache.org> on 2020/06/23 16:03:00 UTC

[jira] [Commented] (SOLR-12698) SolrFeature: no-fq optimisation

    [ https://issues.apache.org/jira/browse/SOLR-12698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143069#comment-17143069 ] 

Christine Poerschke commented on SOLR-12698:
--------------------------------------------

Returning to this. Looks like [~dsmiley]'s SOLR-14364 and SOLR-14376 changes did an equivalent alternative no-fq optimisation in the meantime.

> SolrFeature: no-fq optimisation
> -------------------------------
>
>                 Key: SOLR-12698
>                 URL: https://issues.apache.org/jira/browse/SOLR-12698
>             Project: Solr
>          Issue Type: Sub-task
>          Components: contrib - LTR
>            Reporter: Stanislav Livotov
>            Priority: Major
>         Attachments: SOLR-12698.patch
>
>
> [~slivotov] wrote in SOLR-12688:
> bq. ... SolrFeature was not optimally implemented for the case when no fq parameter was passed. I'm not absolutely sure what was the intention to introduce both q(which is supposed to be a function query) and fq parameter for the same SolrFeature at all(Is there a case when they will be used together ? ), so I decided not to change behavior but just optimize described case ...
> (Please see SOLR-12688 description for overall context and analysis results.)



--
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