couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1391) Implement _security as _local doc with revision trees
Date Fri, 27 Jan 2012 23:16:10 GMT


Randall Leeds commented on COUCHDB-1391:

Cool. Good plans. You're right not to go crazy with refactoring yet.

I think update_local_docs needs the privileged #db handle, you should just take the local_docs_btree
from the #db it returns and put that into the original handle passed into init_security.
> Implement _security as _local doc with revision trees
> -----------------------------------------------------
>                 Key: COUCHDB-1391
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Paul Joseph Davis
>         Attachments: 0001-Refactor-revision-merging.patch, 0002-Replace-_local-doc-sequence-with-revision-trees.patch,
0003-Prevent-multiple-updates-to-a-single-_local-doc.patch, 0004-Implement-_security-as-a-_local-doc.patch
> We had a discussion [1] a while back about updating the _security object so that it could
be replicated (internally) in a cluster or similar environment. The basic gist was "update
_local docs to have a revision tree, update _security to be a _local doc with docid "_local/_security"
and keep the current _security API for a version or two for backwards compatibility (or forever,
what color is your bike shed?)"
> So I did that.
> Basic patch progression is:
> 1. Refactor revision merging logic so that we can split it out of couch_db_updater's
code path for updating normal docs.
> 2. Implement _local docs with #full_doc_info{} records (and thus revision trees)
> 3. Implement _security as _local/_security
> These things are done. Tests should theoretically pass after each patch but I haven't
gone back and tried. They definitely pass (minus auth_cache which I just submitted a fix for)
now except for replication.js appears to fail for random reasons. I can't quite decide if
I've introduced this or if it just fails randomly. Rather than run it a lot more times and
continue to be confused I'm starting this ticket so I can have other people test and tell
me their results.
> Also, the test suite is rather wonky on trunk with segfaults. We should really look into
that more.
> Patches forth coming. I've also pushed the branch to [2].
> [1]
> [2];a=log;h=refs/heads/new-security-object

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message