You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2015/03/12 19:49:38 UTC

[jira] [Commented] (SOLR-7238) SolrQueryRequest.forward is buggy

    [ https://issues.apache.org/jira/browse/SOLR-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359161#comment-14359161 ] 

Yonik Seeley commented on SOLR-7238:
------------------------------------

The current Solr uses are all in BlobHandler.
The one using "/get" is probably OK (just based on the current implementation of that handler), but the other two uses that use the query component can return the wrong document due to internal ids shifting across searcher versions.

> SolrQueryRequest.forward is buggy
> ---------------------------------
>
>                 Key: SOLR-7238
>                 URL: https://issues.apache.org/jira/browse/SOLR-7238
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.0
>            Reporter: Yonik Seeley
>
> The current API/implementation has a number of potential issues, including encouraging the use of the response object after the locally created request object has been closed, and the fact that the "child" request has no actual relationship with the "parent" request, meaning that either the searcher or the schema objects could change.  A searcher changing would most commonly manifest as incorrect documents being returned or other random exceptions during the writing of the response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org