You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
…tionRepository via StoreEvents and found some potential issues (but nothing that could explain the observed issues); Improved logging in the ConversationIndexer
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
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
v0.7.3
The text was updated successfully, but these errors were encountered: