Use the right escape value when creating the pagination searcher #87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When calling
searcher.pager()
for the Solr service the newly returned searcher was always usingdefaultSolrConfig
as config options, ignoring theescapeQuery
option.Most of the time this is not an issue because queries are escaped by default. I hit this issue while using quepid with a query like
field:(term)
, and the second batch of results would use the escaped query:field\:\(term\)
.This causes that while the first page loads the desired results. If we navigate to the second page a potentially different result set would be returned.