[
https://issues.apache.org/jira/browse/SOLR-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Mandanapu updated SOLR-17393:
------------------------------------
Description:
Noticed that solr suggester is not rendering results in correct order for a
collection with multiple shards defined with below config -
+lookupImpl+ - AnalyzingLookupFactory
+dictionaryImpl+ - DocumentDictionaryFactory
For Example - for a given search term say 'TEST', below query for a collection
named 'COLLECTION' with multiple shards is not rendering search results in
correct order i.e closest match to search term is not showing up in top.
However, if the collection is configured as single shard, working correctly.
https://<SOLR_HOST>/<COLLECTION>/suggest?indent=true&suggest.q=TEST&suggest.lookupImpl=AnalyzingLookupFactory
+Example scenario+ -
For a collection with 5 documents say with terms TEST, TEST123, TEST_123,
TEST1234, TESTING, we expect top search result to be as TEST however we are
noticing different inconsistent results every time suggest is built against a
collection with multiple shards.
was:
Noticed that solr suggester is not rendering results in correct order for a
collection with multiple shards defined with below config -
+lookupImpl+ - AnalyzingLookupFactory
+dictionaryImpl+ - DocumentDictionaryFactory
For Example - for a given search term say 'TEST', below query for a collection
named 'COLLECTION' with multiple shards is not rendering search results in
correct order i.e closest match to search term is not showing up in top.
However, if the collection is configured as single shard, working correctly.
https://<SOLR_HOST>/<COLLECTION>/suggest?indent=true&suggest.q=TEST&suggest.lookupImpl=AnalyzingLookupFactory
+Example scenario+ -
For a collection with 5 documents say with terms TEST, TEST123, TEST_123,
TEST1234, TESTING, we expect top search result to be as TEST however we are
noticing a different inconsistent result every time suggest is built against a
collection with multiple shards.
> Solr Suggester not working as expected for collection with multiple
> shards(distributed search)
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-17393
> URL: https://issues.apache.org/jira/browse/SOLR-17393
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Suggester
> Affects Versions: 9.2.1
> Reporter: Rakesh Mandanapu
> Priority: Major
> Labels: solrclient
>
> Noticed that solr suggester is not rendering results in correct order for a
> collection with multiple shards defined with below config -
> +lookupImpl+ - AnalyzingLookupFactory
> +dictionaryImpl+ - DocumentDictionaryFactory
> For Example - for a given search term say 'TEST', below query for a
> collection named 'COLLECTION' with multiple shards is not rendering search
> results in correct order i.e closest match to search term is not showing up
> in top. However, if the collection is configured as single shard, working
> correctly.
> https://<SOLR_HOST>/<COLLECTION>/suggest?indent=true&suggest.q=TEST&suggest.lookupImpl=AnalyzingLookupFactory
> +Example scenario+ -
> For a collection with 5 documents say with terms TEST, TEST123, TEST_123,
> TEST1234, TESTING, we expect top search result to be as TEST however we are
> noticing different inconsistent results every time suggest is built against a
> collection with multiple shards.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
