[
https://issues.apache.org/jira/browse/SOLR-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067295#comment-13067295
]
Michael McCandless commented on SOLR-2656:
------------------------------------------
The approach here is to always reopen the reader on-demand when a RT get
arrives, ie, if any changes had been made to the index with IndexWriter?
Could you use IR.isCurrent instead of tracking your own generation?
But, stepping back, this approach (open new NRT reader on demand) seems
dangerous? Ie perf will be poor if a client has one thread constantly updating
and another constantly doing RT get?
Maybe we should use NRTManager, or its approach, here? Ie, rate limit the
reopens, so that if there are too many gets, they are batched up and we only
reopen "periodically" (which can still be relatively frequent).
Maybe we should call this near-real-time get?
> realtime get
> ------------
>
> Key: SOLR-2656
> URL: https://issues.apache.org/jira/browse/SOLR-2656
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Attachments: SOLR-2656.patch
>
>
> Provide a non point-in-time interface to get a document.
> For example, if you add a new document, you will be able to get it,
> regardless of if the searcher has been refreshed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
