Since the default is staying with random, I see no reason not to commit it today :)
B. On Wed, Sep 9, 2009 at 5:21 PM, Adam Kocoloski (JIRA)<j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/COUCHDB-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Adam Kocoloski updated COUCHDB-465: > ----------------------------------- > > Fix Version/s: 0.11 > > Yes, this is going into 0.11. It looks like things have stabilized; is there > any reason not to commit it today? > >> Produce sequential, but unique, document id's >> --------------------------------------------- >> >> Key: COUCHDB-465 >> URL: https://issues.apache.org/jira/browse/COUCHDB-465 >> Project: CouchDB >> Issue Type: Improvement >> Reporter: Robert Newson >> Fix For: 0.11 >> >> Attachments: 041-uuid-gen-seq.ini, 041-uuid-gen-utc.ini, >> 041-uuid-gen.t, couch_uuids.patch, uuid_generator.patch >> >> >> Currently, if the client does not specify an id (POST'ing a single document >> or using _bulk_docs) a random 16 byte value is created. This kind of key is >> particularly brutal on b+tree updates and the append-only nature of couchdb >> files. >> Attached is a patch to change this to a two-part identifier. The first part >> is a random 12 byte value and the remainder is a counter. The random prefix >> is rerandomized when the counter reaches its maximum. The rollover in the >> patch is at 16 million but can obviously be changed. The upshot is that the >> b+tree is updated in a better fashion, which should lead to performance >> benefits. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
