[
https://issues.apache.org/jira/browse/SOLR-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas DiPiazza updated SOLR-13426:
-------------------------------------
Description:
I noticed that Solr will allow you to run a graph query when the limitation on
nodes/shards is not agreed to.
see:
https://lucene.apache.org/solr/guide/6_6/other-parsers.html#OtherParsers-Limitations.1
bq. Limitations
bq. The graph parser only works in single node Solr installations, or with
SolrCloud collections that use exactly 1 shard.
bq.
This will result in no error, and the query results will be incorrect. This
leads you to thinking everything is fine until you realize the issue later on.
Is it possible to throw an error to force people to meet these limitations?
was:
I noticed that solr will allow you to run a graph query against a collection
that has multiple shards.
This will result in no error and incorrect query results.
Is it possible to throw an error to force people to use shards=1 for graph
query parser?
Will prevent someone from accidentally using graph query parser in a situation
where it will return really misleading results.
> Solr graph queries - should error when run in multiple shard collections?
> -------------------------------------------------------------------------
>
> Key: SOLR-13426
> URL: https://issues.apache.org/jira/browse/SOLR-13426
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers
> Affects Versions: 7.7.1
> Reporter: Nicholas DiPiazza
> Priority: Major
>
> I noticed that Solr will allow you to run a graph query when the limitation
> on nodes/shards is not agreed to.
> see:
> https://lucene.apache.org/solr/guide/6_6/other-parsers.html#OtherParsers-Limitations.1
>
> bq. Limitations
> bq. The graph parser only works in single node Solr installations, or with
> SolrCloud collections that use exactly 1 shard.
> bq.
> This will result in no error, and the query results will be incorrect. This
> leads you to thinking everything is fine until you realize the issue later on.
> Is it possible to throw an error to force people to meet these limitations?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
