[
https://issues.apache.org/jira/browse/COUCHDB-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lehnardt resolved COUCHDB-1279.
-----------------------------------
Resolution: Not A Problem
Hey, thanks for the report. This is definitely Couchbase 2.0 related, but
currently this works according to spec (and is not a bug) of Couchbase 2.0
(think of the definition of a view as being always stale=ok in CouchDB-land),
we are working towards mirroring the CouchDB API fully but we are not there yet.
Closing this one then.
> Deleted documents persist in View results
> -----------------------------------------
>
> Key: COUCHDB-1279
> URL: https://issues.apache.org/jira/browse/COUCHDB-1279
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 1.2
> Environment: OS X 10.6.8, Couchbase Server 2.0.0-dev4
> Reporter: Chris Gomez
> Priority: Blocker
>
> Previously deleted documents are returned as results in a View.
> View results yield { error: not_found, reason: deleted } when queried by id
> and are not returned in _all_docs.
> Compacting the database does not fix the issue. Deleting the View and
> rebuilding did not fix the issue. Deleting the view then compacting, then
> rebuilding the view did not fix the issue. Currently, the only way I know how
> to get around it is to delete/rebuild the database.
> These documents would have been deleted programmatically, so I can't be
> certain about the exact create/update/delete scenario the have gone through.
> These particular documents could have been around for a long while before I
> even noticed them. The biggest issue I have with this bug is that it means I
> can't bulk delete any documents when this bug occurs because of the update
> conflict it creates.
> May be related:
> http://stackoverflow.com/questions/7323285/couchdb-views-not-being-updated-after-delete
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
