You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Mike Drob (Jira)" <ji...@apache.org> on 2021/02/22 23:14:00 UTC
[jira] [Updated] (SOLR-15180) SearchHandler could prune uniqueKey
queries
[ https://issues.apache.org/jira/browse/SOLR-15180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Drob updated SOLR-15180:
-----------------------------
Description:
When doing a query that includes an {{id}}, we should be able to prune which shards need to be distributed to.
This can be done explicitly by the user with {{_route\_}}, but I think Solr should be able to automatically infer that value in some cases.
Other wish list items: we can potentially apply this to filter queries as well, or to aliases.
The real-time-get handler already does intelligent routing to query only the relevant shards, hopefully that logic can be re-used.
was:
When doing a query that includes an {{id}}, we should be able to prune which shards need to be distributed to.
This can be done explicitly by the user with {{_route_}}, but I think Solr should be able to automatically infer that value in some cases.
Other wish list items: we can potentially apply this to filter queries as well, or to aliases.
The real-time-get handler already does intelligent routing to query only the relevant shards, hopefully that logic can be re-used.
> SearchHandler could prune uniqueKey queries
> -------------------------------------------
>
> Key: SOLR-15180
> URL: https://issues.apache.org/jira/browse/SOLR-15180
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
> Reporter: Mike Drob
> Priority: Major
>
> When doing a query that includes an {{id}}, we should be able to prune which shards need to be distributed to.
> This can be done explicitly by the user with {{_route\_}}, but I think Solr should be able to automatically infer that value in some cases.
> Other wish list items: we can potentially apply this to filter queries as well, or to aliases.
> The real-time-get handler already does intelligent routing to query only the relevant shards, hopefully that logic can be re-used.
--
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