[
https://issues.apache.org/jira/browse/SOLR-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067397#comment-13067397
]
Yonik Seeley commented on SOLR-2656:
------------------------------------
bq. I am disputing that it's really "real-time" given that it's built on top of
"near-real-time". Ie calling this real-time is over-selling
it, I think; the performance will not be great?
Another way of thinking about the naming is that NRT returns you data with a
low degree of staleness. Realtime means no staleness.
no-staleness-get doesn't quite have the same catchiness as realtime-get ;-)
bq. Another thing to consider is NRTCachingDir
I had sort of assumed that would become a lucene default. If not, we should
definitely make it available in Solr.
bq. What kind of "clocks" would one want to plug in here?
A client could use this to accept some degree of staleness (more useful if
clocks have a relation to real time, or if the internal clock on updates was
returned to clients). I was more thinking of future internal uses though -
like if we need to retrieve the version of a doc (or other information about
it), and we keep track of the last update clock that updated a block of ids,
then we can use that to avoid unnecessary re-opens.
bq. Maybe Solr should use a transaction log
Yep, that's the idea (we need it for both recovery and durability).
> 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]
