[PYCBC-176] merge the 1.1 updated documentation into docs templates Created: 21/Aug/13  Updated: 25/Sep/13

Status: Open
Project: Couchbase Python Client Library
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.0
Security Level: Public

Type: Task Priority: Blocker
Reporter: Matt Ingenthron Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Need the updated documentation with 1.1 to be merged into the main docs.

Mark: this is assigned to you because you have supplied it, but Amy needs some guidance on how to handle the merge. The problem is that your generated docs make changes to the section of docs that had been previously edited and are part of the 1.0 docs.

Guidance needed: can you either generate just the 1.1 changed set, or let us know that it'll have to be manually merged. Also, how will we handle this going forward.

 Comments   
Comment by Mark Nunberg [ 25/Sep/13 ]
I really have no idea what this means. Traditionally my pattern with writing the docs has been to generate XML and stuff it inside the docs repo, with the other toolchain there applying the necessary formatting.

Feel free to reassign this to amy or close this if that's all that needs to be done on my part.




[PYCBC-250] support for distributing data by hashkey Created: 03/Jul/14  Updated: 12/Sep/14

Status: Open
Project: Couchbase Python Client Library
Component/s: apidocs, docs, library
Affects Version/s: None
Fix Version/s: .future
Security Level: Public

Type: New Feature Priority: Major
Reporter: Matt Ingenthron Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 0
Labels: customer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates to
relates to JCBC-549 Implement setHashAlg() / Implement ab... Open

 Description   
In some situations, users would like to co-locate related data to ensure that failure of a node would affect only related data, rather than a single node failure affecting possibly all user's data. This is referring to supporting the 'hashkey' function that exists in libcouchbase.

 Comments   
Comment by Matt Ingenthron [ 03/Jul/14 ]
Note that I've assigned this to myself as this would need to be considered as part of a bigger change. Couchbase Server is not tested in this fashion where data may be unevenly distributed and having this supported by some clients and not others would be a concern. I wanted to track the request for this feature, however, so I've posted it here.




Generated at Mon Sep 22 01:03:32 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.