Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

Conversation search endpoint returns inconsistent number of results #256

Open
Peym4n opened this issue Jun 12, 2018 · 2 comments
Open

Conversation search endpoint returns inconsistent number of results #256

Peym4n opened this issue Jun 12, 2018 · 2 comments
Assignees
Milestone

Comments

@Peym4n
Copy link
Contributor

Peym4n commented Jun 12, 2018

Expected Behaviour

The returned number of results (numFound) should stay the same between each request, when no new messages were added.

Actual Behaviour

The returned number of results (numFound) changes unexpectedly (decrease and increase by 1) after each request, even when no new messages were added.

Environment

  • Smarti-Version: v0.7.3
@Peym4n Peym4n added the bug label Jun 12, 2018
@Peym4n Peym4n added this to the v0.7.4 milestone Jun 12, 2018
@Peym4n Peym4n added the ready label Jun 12, 2018
@westei westei modified the milestones: v0.7.4, v0.7.5 Jun 13, 2018
@westei westei added in progress and removed ready labels Jun 13, 2018
westei added a commit that referenced this issue Jun 14, 2018
…tionRepository via StoreEvents and found some potential issues (but nothing that could explain the observed issues); Improved logging in the ConversationIndexer
@westei westei modified the milestones: v0.7.5, v0.7.6, v0.7.7 Jun 14, 2018
@westei
Copy link
Member

westei commented Jun 25, 2018

As this might be releated to the embedded Solr server we will delay this until we switched to en external Solr Server (see SolrCloud support)

@westei westei modified the milestones: v0.7.7, v0.8.0 Jun 25, 2018
@westei westei added ready and removed in progress labels Jun 25, 2018
@westei westei modified the milestones: v0.8.0, v0.9.0 Sep 24, 2018
@westei
Copy link
Member

westei commented Mar 29, 2019

Their are two reasons why this can happen:

  1. This Query Provider performs a query in Solr and loads the Data from the MongoDB. If Solr provides a result that is not present in the MongoDB it gets filtered. So if the Solr <-> MongoDB is not in Sync the number of actual results can differ from the numFound in Solr
  2. This Query Provider uses contextual information for the query. So the Results context may overlap. If this is the case unique results of the Solr query are merged into a single result. In case of merged results the actual results may be less as the numFound provided by Solr.

Both cases can only be solved if we re-implement this query provider to work solely on the Solr Index. While this was not possible with 0.8.0 the Conversation Index updates #302 implemented for 0.9.0 and espacialy the Conversation Segmentation part of #303 could now support such an implementation (as it is now possible to avoid overlapping Solr Results using Solr collapse/expand functionality)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants