[
https://issues.apache.org/jira/browse/SOLR-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606483#action_12606483
]
Yonik Seeley commented on SOLR-502:
-----------------------------------
I see your point on the overlap between something like QueryCommand and
ResponseBuilder... but ResponseBuilder feels like it's at a higher level. Say
that a custom component or handler wants to do a couple queries... or different
queries depending on the results of the first query (or something like
unsupervised feedback). Should a different ResponseBuilder object be built for
each query that is part of a request/response?
ResponseBuilder is also a bit big and ill-defined (but currently gets the job
done for communication between different query components). Upgrading it to
serve as something you pass to a SolrIndexSearcher to do a query doesn't feel
quite right (or at least that's not the way I've been thinking about it).
> Add search time out support
> ---------------------------
>
> Key: SOLR-502
> URL: https://issues.apache.org/jira/browse/SOLR-502
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Sean Timm
> Assignee: Otis Gospodnetic
> Priority: Minor
> Fix For: 1.3
>
> Attachments: SOLR-502.patch, SOLR-502.patch, SOLR-502.patch,
> SOLR-502.patch, SOLR-502.patch, solrTimeout.patch, solrTimeout.patch,
> solrTimeout.patch, solrTimeout.patch, solrTimeout.patch
>
>
> Uses LUCENE-997 to add time out support to Solr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
