lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-3516) Should provide mechanism for clients to see if currentSearcher is "newest" available
Date Thu, 07 Jun 2012 02:17:23 GMT
Hoss Man created SOLR-3516:
------------------------------

             Summary: Should provide mechanism for clients to see if currentSearcher is "newest"
available
                 Key: SOLR-3516
                 URL: https://issues.apache.org/jira/browse/SOLR-3516
             Project: Solr
          Issue Type: Improvement
            Reporter: Hoss Man


With the introduction of the "openSearcher=(true|false)" option on commit & autocommit,
there doesn't seem to be any way for external clients to know if the current searcher is the
newest possible searcher available - ie: will "commit=true&openSearcher=true" (w/o any
other changes) affect the results of queries?

We should probably add some way of determining this programmaticly (and via the Admin UI)
as a stat to either the SolrCore or the individual "searchers".  Alternatively it might be
enough to just report some piece of metadata about the commit point in the searcher and in
the updateHandler that could be compared.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message