[PYCBC-228] persist_to and replicate_to mismatched Created: 13/Feb/14  Updated: 17/Apr/14  Resolved: 19/Feb/14

Status: Resolved
Project: Couchbase Python Client Library
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: .next
Security Level: Public

Type: Task Priority: Critical
Reporter: Mark Nunberg Assignee: Mark Nunberg
Resolution: Fixed Votes: 0
Labels: customer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
Duplicate
is duplicated by PYCBC-242 set call does not correct assign repl... Resolved

 Description   
The persist_to and replicate_to arguments are mismatched in the set() operation, thus persist_to means replicate_to and vice versa

 Comments   
Comment by Mark Nunberg [ 13/Feb/14 ]
http://review.couchbase.org/#/c/33489/




[PYCBC-242] set call does not correct assign replicate_to and assign_to Created: 17/Apr/14  Updated: 17/Apr/14  Resolved: 17/Apr/14

Status: Resolved
Project: Couchbase Python Client Library
Component/s: library
Affects Version/s: 1.2.0
Fix Version/s: .next
Security Level: Public

Type: Task Priority: Major
Reporter: Daniel Owen Assignee: Daniel Owen
Resolution: Duplicate Votes: 0
Labels: customer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File python-cb.set.py    
Issue Links:
Duplicate
duplicates PYCBC-228 persist_to and replicate_to mismatched Resolved

 Description   
Defect resides in couchbase-python-client/couchbase/connection.py

In function set (line number 257).
The return code is (line number 330 & 331)

         return _Base.set(self, key, value, cas, ttl, format,
                         persist_to, replicate_to)

however should be...

return _Base.set(self, key, value, cas, ttl, format,
                         persist_to=persist_to, replicate_to=replicate_to)

The attached program can be used to demonstrate the problem.

 Comments   
Comment by Mark Nunberg [ 17/Apr/14 ]
https://www.couchbase.com/issues/browse/PYCBC-228




[PYCBC-229] Example for mapkey_single is wrong Created: 17/Feb/14  Updated: 14/Apr/14  Resolved: 14/Apr/14

Status: Resolved
Project: Couchbase Python Client Library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: .next
Security Level: Public

Type: Task Priority: Major
Reporter: Patrick Varley Assignee: Mark Nunberg
Resolution: Fixed Votes: 0
Labels: documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: http://www.couchbase.com/autodocs/couchbase-python-client-1.2.0/html/api/views.html#couchbase.views.params.Query.mapkey_single


 Description   
The examples uses this:

q.mapkey_single = ["abbaye_de_maredsous"]

It should be:

q.mapkey_single = "abbaye_de_maredsous"

The 1st one creates the following url options:
'key=%5B%22abbaye_de_maredsous22%5D'

Where %5B and %5D are the square brackets.

 Comments   
Comment by Mark Nunberg [ 14/Apr/14 ]
http://review.couchbase.org/35693




[PYCBC-222] gevent is still listed as experimental in the API doc Created: 14/Jan/14  Updated: 14/Apr/14

Status: In Progress
Project: Couchbase Python Client Library
Component/s: apidocs
Affects Version/s: 1.2.0
Fix Version/s: .next
Security Level: Public

Type: Bug Priority: Major
Reporter: Matt Ingenthron Assignee: Mark Nunberg
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I happened to notice in the connect() that gevent is still listed as experimental. This is supported as of 1.2.0, correct?

 Comments   
Comment by Mark Nunberg [ 14/Jan/14 ]
Yes, the API itself is experimental. It's supported but experimental.
Comment by Mark Nunberg [ 14/Jan/14 ]
This will go away in 1.2.1; though gevent is inherently experimental.
Comment by Mark Nunberg [ 14/Apr/14 ]
http://review.couchbase.org/35692




[PYCBC-231] Use compact JSON encoding for Python objects Created: 25/Feb/14  Updated: 14/Apr/14

Status: Open
Project: Couchbase Python Client Library
Component/s: library
Affects Version/s: 1.2.0
Fix Version/s: .next
Security Level: Public

Type: Improvement Priority: Major
Reporter: Dave Rigby Assignee: Mark Nunberg
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency

 Description   
When encoding Python objects to JSON, we currently use json.dumps() with default arguments. This produces JSON encoded with spaces separating fields. This is somewhat wasteful from a memory / disk / network utilisation point of view.

More preferable would be to use a "compact" encoding which removes all spaces - this can be achieved using separators=(',', ':') or similar (see http://docs.python.org/2/library/json.html).






[PYCBC-239] Docs: transcoder improvement Created: 25/Mar/14  Updated: 14/Apr/14

Status: Open
Project: Couchbase Python Client Library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: .next
Security Level: Public

Type: Bug Priority: Minor
Reporter: Perry Krug Assignee: Mark Nunberg
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File patch.diff    

 Description   
I think there's an error in the Python SDK Advanced
Usage page.
Under the Custom Transcoder Objects section:
http://docs.couchbase.com/couchbase-sdk-python-1.2/#custom-transcoder-objects

New to Python and to Couchbase I've been playing around, but was struggling
to get this to work.
I believe the problem is two folds (ignoring the lack of 1import Couchbase`
and `import FMT_BYTES` as this is only a snippet):
- use of `format` instead of `flags` in `decode_value()`
- not converting "long value" to bytes

Please find attached a patch which, if I am correct, I think would save
time, and avoid confusion, to newcomers like me.




[PYCBC-241] Use new "Semantic Errors" from libcouchbase 2.3.0 Created: 14/Apr/14  Updated: 14/Apr/14

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

Type: Task Priority: Critical
Reporter: Mark Nunberg Assignee: Mark Nunberg
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Comments   
Comment by Mark Nunberg [ 14/Apr/14 ]
http://review.couchbase.org/#/c/35689/




Generated at Fri Apr 18 06:51:05 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.