You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Sven Helmberger (JIRA)" <ji...@apache.org> on 2009/03/21 13:04:50 UTC
[jira] Created: (COUCHDB-300) Update Sequence broken
Update Sequence broken
----------------------
Key: COUCHDB-300
URL: https://issues.apache.org/jira/browse/COUCHDB-300
Project: CouchDB
Issue Type: Bug
Environment: ubuntu hardy
Reporter: Sven Helmberger
Fix For: 0.9
Attachments: update_seq_kaputt.js
Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-300) Update Sequence broken
Posted by "Damien Katz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688024#action_12688024 ]
Damien Katz commented on COUCHDB-300:
-------------------------------------
Sven, you can still find all the documents in the database by scanning the _all_docs view. Load and reopen each doc by name.
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-300) Update Sequence broken
Posted by "Sven Helmberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688025#action_12688025 ]
Sven Helmberger commented on COUCHDB-300:
-----------------------------------------
I understand that. I just wanted to point out that my initial intent for using the _all_docs_by_seq view is to know which documents have changed.
So I know for example what action to execute with a changed document. The fact that the document is missing prevents me from knowing it has changed.
So in order for this idea to work I would need to touch the document for every update conflict I catch in my app and hope no one screws up things by changing the database from the outside of the app.
That doesn't sound good to me.
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (COUCHDB-300) Update Sequence broken
Posted by "Damien Katz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damien Katz resolved COUCHDB-300.
---------------------------------
Resolution: Fixed
This is an old bug, but recent changes made it happen on most conflicts, instead of occasional conflicts.
For any database that's gotten itself in this state, this should be fixable by touching (load and save) the affected docs in the database (or all the docs in the database).
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-300) Update Sequence broken
Posted by "Sven Helmberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Helmberger updated COUCHDB-300:
------------------------------------
Attachment: update_seq_kaputt.js
Testcase that shows the bug
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-300) Update Sequence broken
Posted by "Sven Helmberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688023#action_12688023 ]
Sven Helmberger commented on COUCHDB-300:
-----------------------------------------
But if I use _all_docs_by_seq to know what documents have changed, I don't know that I have to touch the document to fix things because it's missing from _all_docs_by_seq. Isn't that a bit of a problem?
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-300) Update Sequence broken
Posted by "Sven Helmberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688029#action_12688029 ]
Sven Helmberger commented on COUCHDB-300:
-----------------------------------------
Oh.. sorry.. I totally misunderstood..
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-300) Update Sequence broken
Posted by "Jan Lehnardt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Lehnardt updated COUCHDB-300:
---------------------------------
Attachment: all_docs_by_seq.js
Fixed testcase.
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-300) Update Sequence broken
Posted by "Damien Katz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688028#action_12688028 ]
Damien Katz commented on COUCHDB-300:
-------------------------------------
Sven, I think you missed the fix checked in for this bug? The fix prevents databases from getting into this state.
But if you already have a database in this state, you can fix it by touching all the docs (or just the affected one). It's a one time thing.
> Update Sequence broken
> ----------------------
>
> Key: COUCHDB-300
> URL: https://issues.apache.org/jira/browse/COUCHDB-300
> Project: CouchDB
> Issue Type: Bug
> Environment: ubuntu hardy
> Reporter: Sven Helmberger
> Fix For: 0.9
>
> Attachments: all_docs_by_seq.js, update_seq_kaputt.js
>
>
> Database gets into a state where there is one document but an empty update sequence.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.