[ https://issues.apache.org/jira/browse/COUCHDB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Anderson closed COUCHDB-77. --------------------------------- Resolution: Fixed documented on http://wiki.apache.org/couchdb/HTTP_view_API > Querying views with update=false should not update views > -------------------------------------------------------- > > Key: COUCHDB-77 > URL: https://issues.apache.org/jira/browse/COUCHDB-77 > Project: CouchDB > Issue Type: Bug > Components: Database Core, Documentation > Reporter: Chris Anderson > Assignee: Chris Anderson > Priority: Blocker > Fix For: 0.9 > > > Querying a view with update=false should respond immediately with results > from the latest available view index, even if the view is currently being > updated for another request. Sometimes stale data is better than data that > could possibly take forever. > Looking through the code my guess is that update=false is being dropped on > the floor somewhere between the http request parser and the actual view > response generation code. Wish I could say for sure why it's not working, but > I've verified that .view files are modified even when update=false is passed > in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.