[
https://issues.apache.org/jira/browse/SOLR-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743946#comment-17743946
]
Houston Putman commented on SOLR-16856:
---------------------------------------
{quote}It could be interesting if Solr search responses included a header flag
to let you know that there are pending changes not yet visible. It would
particularly stand-out in a zero-result query.
{quote}
That would be a cool feature!
> Use autoSoftCommit with the default configSet
> ---------------------------------------------
>
> Key: SOLR-16856
> URL: https://issues.apache.org/jira/browse/SOLR-16856
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Houston Putman
> Assignee: Houston Putman
> Priority: Major
> Fix For: 9.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The default autoCommit/autoSoftCommit settings that ship with Solr's default
> configSet are listed as such:
>
> <autoCommit>
> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
> <openSearcher>false</openSearcher>
> </autoCommit>
> <autoSoftCommit>
> <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
> </autoSoftCommit>
>
> With "openSearcher" set to false on the autoCommit, and no autoSoftCommit
> being used, there is little guarantee as to when users can expect to see
> their documents returned from Solr.
>
> We should use a pretty NRT-ish number for the default autoSoftCommit, like
> 3000.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
