couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Markham (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1279) Deleted documents persist in View results
Date Tue, 13 Sep 2011 11:30:10 GMT


Alex Markham commented on COUCHDB-1279:

We have noticed this on couch 1.0.3 on centos 64bit - possibly spidermonkey 1.9.2

Where deleted docs removed by adding "_deleted":true would still show in views. 
We have multiple couches replicating in our system and this would appear irregularly, with
some deleted documents showing in views on some couches and not on others without any obvious
Removing the document attachments before adding "_deleted":true seemed to reduce the frequency
of this occurring.

I even tried deleting the view cache file (.view) and reindexing the whole view on one couch,
but it still showed the issue, even showing the _deleted_conflicts field on some.
The old views were from b 1.0.2, but when we added new views  after the update to 1.0.3 (with
the same functions), the problem seemed to go away.

> Deleted documents persist in View results
> -----------------------------------------
>                 Key: COUCHDB-1279
>                 URL:
>             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:

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message