Yes, I didn't copy all our code but we also do extraReq.close(); in a
finally block. It was not the problem.
On 04/19/2017 11:53 AM, Mikhail Khludnev wrote:
If you create SolrQueryRequest make sure you close it then, since it's
necessary to release a searcher.
On Wed, Apr 19, 2017 at 12:35 PM,
If you create SolrQueryRequest make sure you close it then, since it's
necessary to release a searcher.
On Wed, Apr 19, 2017 at 12:35 PM, Elodie Sannier
wrote:
> Hello,
>
> We have found how to fix the problem.
> When we update the original SolrQueryResponse object, we need to create
> a new Bas
Hello,
We have found how to fix the problem.
When we update the original SolrQueryResponse object, we need to create
a new BasicResultContext object with the extra response.
Simplified code :
public class CustomSearchHandler extends SearchHandler {
public void handleRequestBody(SolrQueryReques
Hi Gerald
The best solution in my mind is to look at the custom code and try to find a
way to remove it from your system. Solr queries can be complex, and I hope
there is a way to get the results you need. Would you like to say what results
you want to get, and what Solr queries you have tried?
On 4/7/2017 3:09 AM, Gerald Reinhart wrote:
>We have some custom code that extends SearchHandler to be able to :
> - do an extra request
> - merge/combine the original request and the extra request
> results
>
>On Solr 5.x, our code was working very well, now with Solr 6.x w
Hi,
We have some custom code that extends SearchHandler to be able to :
- do an extra request
- merge/combine the original request and the extra request results
On Solr 5.x, our code was working very well, now with Solr 6.x we
have the following issue: the number of SolrI
