[CCBC-503] need better documentation on how to use error classifiers Created: 28/Aug/14  Updated: 28/Aug/14

Status: Open
Project: Couchbase C client library libcouchbase
Component/s: docs
Affects Version/s: 2.4.0, 2.4.1
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
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   
Documentation has a section on error handling, but there's nothing in the documentation other than a release note on error classifiers.

Please add some detail on what these are and how they're intended to be used.

 Comments   
Comment by Mark Nunberg [ 28/Aug/14 ]
http://docs.couchbase.com/couchbase-sdk-c-2.4/index.html#error-handling-and-diagnostics gives a pretty detailed explanation. Do you mean to add an additional section within the API docs, or something else?




[CCBC-502] Provide API to retrieve bucket name Created: 27/Aug/14  Updated: 27/Aug/14

Status: Open
Project: Couchbase C client library libcouchbase
Component/s: None
Affects Version/s: None
Fix Version/s: 2.4.2
Security Level: Public

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


 Description   
This should be a simple cntl to retrieve the name of the bucket as a string :)




[CCBC-501] Hide no_verify SSL option Created: 25/Aug/14  Updated: 26/Aug/14  Resolved: 26/Aug/14

Status: Resolved
Project: Couchbase C client library libcouchbase
Component/s: library
Affects Version/s: 2.4.0
Fix Version/s: 2.4.1
Security Level: Public

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


 Description   
Hide the ssl=no_verify option and rename the capath option to cert_path, as currently the server does not support third-party-signed certificates, but a simple self-signed certificate




[CCBC-500] ConnSpec parser fails to understand a string with a non-existent scheme. Created: 20/Aug/14  Updated: 26/Aug/14  Resolved: 26/Aug/14

Status: Resolved
Project: Couchbase C client library libcouchbase
Component/s: library
Affects Version/s: 2.4.0
Fix Version/s: 2.4.1
Security Level: Public

Type: Task Priority: Major
Reporter: Brett Lawson Assignee: Brett Lawson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
When passing a string that is simply an IP address (ie: `192.168.7.26:8091`), libcouchbase fails with a 'Invalid arguments' error.

 Comments   
Comment by Mark Nunberg [ 20/Aug/14 ]
this is by design. to use a raw address, the v2 structure should be used instead
Comment by Brett Lawson [ 20/Aug/14 ]
A raw address/port combination is a valid URI and a valid connection string, http scheme should be used by default if one is not provided. This is necessary for backwards compatibility and does not have any known side effects.
Comment by Mark Nunberg [ 20/Aug/14 ]
The heuristics here are a bit more complex, and we shouldn't be using HTTP bootstrap by default unless there is good reason to do so, thus for example a traditional 'simple IP' address should end up being CCCP, but if a port is provided, would be HTTP, etc.

In my opinion, if dealing with a higher level SDK, the branching should be done at the SDK level rather than within the client library itself (this way, the SDK has a chance to print out a warning about how using a scheme-less syntax is deprecated, etc). This would work by having the SDK determine if the string starts with a valid scheme, and if it does, use the 'v3' options. If it does not, use the 'v1' options
Comment by Brett Lawson [ 20/Aug/14 ]
Whilst I agree with you, the spec specifically defines a host/port combination as being valid for other reasons (such as easily supporting user upgrades). Breaking spec for a single SDK, especially since it's such a simple change (literally code was added to make this specifically not work) does not make sense.

P.S. Using couchbase:// by default does not permit backwards compatibility with pre-2.5 servers (or it should not be at least, again, for reasons I won't list here; some are mentioned in the spec). Thus defaulting to this on a 'feature' thats sole purpose is supporting lazy initial upgrades also makes no sense.




Generated at Tue Sep 02 02:43:49 CDT 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.