[ 
https://issues.apache.org/jira/browse/COUCHDB-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196751#comment-13196751
 ] 

Paul Joseph Davis commented on COUCHDB-1279:
--------------------------------------------

@Matt,

Can you get me a copy of the db file that exhibits this or shell access to a 
machine that I can build CouchDB on that has a copy of this file? Sounds 
deterministic enough but the fact that so few people have seen it means its 
probably quite the subtle condition.
                
> 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.0.3
>         Environment: CouchDB 1.0.3, Centos 64 bit
>            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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to