[
https://issues.apache.org/jira/browse/COUCHDB-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Leeds resolved COUCHDB-736.
-----------------------------------
Resolution: Won't Fix
It sounds like you're trying to confer some notion of "stability" on the
database-at-the-time-of-first-indexing-request, and asking that *all* those
documents be indexed before any result can be returned. This idea seems bogus
to me, because as future updates arrive the stale index can always again become
a partial index. If you need to be sure the index reflects the state of the db
you should not be using stale=ok :)
> stale-ok view queries can return inconsistent partial results
> -------------------------------------------------------------
>
> Key: COUCHDB-736
> URL: https://issues.apache.org/jira/browse/COUCHDB-736
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Chris Anderson
>
> since r796805 requests to views with the stale=ok option have returned
> partially computed index results. This changed the semantics of views. This
> ticket is about maintaining the old semantics.
> This should be changed so stale=ok only returns what would be returned by a
> normal view request. stale=partial would be an OK name for an option to
> provide the current behavior.
> The best way to fix this would be to store the NewGroup sent on the
> partial_update cast in #group_state.partial_group instead of
> #group_state.group
> This will also eliminate the (rare) changes of serving inconsistent results
> with a regular view query.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
