[RCBC-120] Docs: Reference installation Created: 11/Feb/13  Updated: 11/Feb/13

Status: Open
Project: Couchbase Ruby client library
Component/s: docs
Affects Version/s: 1.2.1
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Customers have lots of choices at their fingertips, and many of those choices will result in a non-functioning installation, or at least a lot of time spent figuring out what the right pieces are.

Can we please provide as much details as possible about a reference installation that we can be sure will work for a customer who is just getting started? This is outside of our support for any one operatin system, but more about telling the customer "if you install with these versions and packages, this code will work"

-OS
-"language" version (Ruby 1.9.3, etc)
-other packages/modules required and/or tested with



[RCBC-119] Error handling documentation Created: 05/Feb/13  Updated: 11/Feb/13

Status: Reopened
Project: Couchbase Ruby client library
Component/s: docs
Affects Version/s: 1.2.1
Fix Version/s: 1.3.0
Security Level: Public

Type: Improvement Priority: Major
Reporter: Perry Krug Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Please create some documentation specifying possible error/failures to operations, what they "look" like in the logs/exceptions/stack traces and what our recommendation is on how to handle them.

i.e. tmp_oom, timeouts (connection/operation/java-internal/etc), "get miss" (it's technically a failure, let's make it overly obvious what it means), CAS failure, add() failure, replace() failure,

Some of this should be covered in the API reference, but this bug is specifically for a single page where this information is aggregated that a customer/user could read about how to handle errors.



[RCBC-103] Improvements to the Getting Started Guide and the Tutorial Created: 20/Dec/12  Updated: 02/May/13

Status: Open
Project: Couchbase Ruby client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: None
Security Level: Public

Type: Improvement Priority: Major
Reporter: Michael Nitschinger Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Ruby Docs

*** Getting Started ***

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/installing_the_couchbase_client_libraries.html
- link broken: ... is libcouchbase. Please consult [C Client Library page about w ...

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/hello_couchbase.html
- In the list where the conn params are explained, maybe explain why I need to ouse the list param
when I have more then one node (where I have to use host?)? Its not really obvious why I have two
different args for the same type.
- Maybe add a quick sentence what marhsal does? Serialzining ruby objects? Note that you cant use
views with it.

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/creating_and_updating_documents.html
- here it talks about the :plain mode and I'm confused, whats the different to :marshal? Maybe
good to explain in a sentence.

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/reading_documents.html
- Where basic view querying is explained, I think we need to add a sentence or two on how
a second HTTP request is maed when you access the design document. Since you ask an array here,
is it prefetched? how does it work? Would be good to know so that people dont use it in a loop
for example.

*** Tutorial **

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/_tl_dr.html
- I think you need to tell people how to install bundler? I have it, but I'm not sure if it comes
by default? If it is always there forget this comment :)

- Sign in with twitter gives me 401 unauthorized.. do we really need this and is it supposed to
work? Otherwise the sample app works out of the box, cool work.

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/_create_application_skeleton.html
- Can you explain the --old-style-hash in a sentence? Dont know what it is?
- The short gem description only contains omniauth-twitter, but the full also omniauth?
- maybe mention to update the dependencies after the changes? bundle update?

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/_implement_controllers.html
- Where you explain the controller functionality: it's not really obvios how the methods map to the
views. What will happen when you access a different method that has no view defined? Just a few
words to explain how the "magical" vie access works would be good I think.

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.2/_bonus_spatial_queries_sessions_and_cache.html
- On caching: will it use the same couchbase client connection or instantiate a new one?

Otherwise good job! :)



[RCBC-66] Ruby Gem 1.1.2/1.1.3 not responding to :node_list param in Couchbase.new||Couchbase.connect Created: 30/Jul/12  Updated: 02/May/13

Status: Open
Project: Couchbase Ruby client library
Component/s: docs, library
Affects Version/s: 1.1.2
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Jasdeep Jaitla Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: I tried it on Amazon Linux with a cluster of two Couchbase 2.0 build 1495's specifying gem versions.


 Description   
:node_list syntax returning:
Connection failed: Connection refused (error=0x17) (Couchbase::Error::Connect)

Direct connection to each node works fine. It also works fine in 1.2.0dp6.

See thread for more info: http://www.couchbase.com/forums/thread/ruby-client-connection-refused-using-nodelist
I confirmed it wasn't working.

 Comments   
Comment by Jasdeep Jaitla [ 30/Jul/12 ]
I tried it in both 1.1.2 and 1.1.3, neither worked. Like I said, it does work in 1.2.0dp6 latest release. Of course I also have a newer libcouchbase (the one required for dp6 of gem).
Comment by Sergey Avseyev [ 31/Jul/12 ]
I thought its kind of feature, not a bug therefore shouldn't be merged into stable branch. there is workaround although. User could create array of hosts and shift and try host checking for connect error
Comment by Jasdeep Jaitla [ 01/Aug/12 ]
Ah, true, I think what is confusing is the docs on github show the syntax but it only works in dp gem... maybe just make a quick note about that?
Comment by Sergey Avseyev [ 02/Aug/12 ]
Could you put the link?



[RCBC-105] Docs: What operating system versions does the ruby gem support? Created: 20/Dec/12  Updated: 06/May/13

Status: Open
Project: Couchbase Ruby client library
Component/s: docs
Affects Version/s: 1.2.0
Fix Version/s: None
Security Level: Public

Type: Bug Priority: Major
Reporter: Perry Krug Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
I seem to be having problems installing this on CentOS 5.8. I'm not sure if that's the problem, but I tried to verify it via our documentation and couldn't find what versions were supported or not.

 Comments   
Comment by Sergey Avseyev [ 06/May/13 ]
couchbase ruby gem depends on ruby 1.8.7+ and libcouchbase (if there are issues with libcouchbase, please report to CCBC)

According to official ruby site ruby 1.9.3 is supported by centos 5 (probably not from official repository, but should work without any problems): https://bugs.ruby-lang.org/projects/ruby-trunk/wiki/SupportedPlatforms#Ruby-193
Comment by Karen Zeller [ 06/May/13 ]
Please add this information to the correct part of the documentation set for Ruby.



[RCBC-128] Ruby 1.3.0 is missing release notes Created: 08/May/13  Updated: 14/May/13

Status: Open
Project: Couchbase Ruby client library
Component/s: docs
Affects Version/s: None
Fix Version/s: None
Security Level: Public

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


 Description   
It may have been an artifact of the order in which docs were integrated, but I don't see release notes in the right place in the current document.

http://www.couchbase.com/docs/couchbase-sdk-ruby-1.3/couchbase-sdk-ruby-rn.html



 Comments   
Comment by Karen Zeller [ 09/May/13 ]
Hi,

So I investigated this last night and discovered all the XML and content are intact and valid for this entire document.

When I generate PDF the content is missing as well as when the XML to HTML conversion happens. I think this is something to do with the Perl parser that does our conversions expecting some setting.

Can you please get someone familiar with Perl to look at this conversion script?


Thanks,

Karen
Comment by Wayne Siu [ 09/May/13 ]
Matt, can you or someone on your team help? Thanks.
Comment by Matt Ingenthron [ 13/May/13 ]
Mark: I know you haven't been in here before, but can you possibly work with Wayne/Karen to help us out to try to fix this? There's some scripting forensics required.
Comment by Mark Nunberg [ 13/May/13 ]
If you can show me the toolchain or give me access to a remote machine (probably the best) where this toolchain is installed, I could help dig into the issue.
Comment by Karen Zeller [ 14/May/13 ]
Here is the toolchain information:

=======


This is the info you wanted for RCBC-128 on the Toolchain for publishing. I set up 1.3 guides and they generate as PDF and HTML but somehow the release notes are not being pulled in during conversion.

There are no failure messages on the server or on my local machine when the build runs, and the XML is clean. You basically just get a blank page in PDF and HTML for the release notes.

The new ruby guide is here, set up according to what Matt/Sergey agreed on content:

https://github.com/couchbase/docs/tree/master/Couchbase/products/couchbase/couchbase-sdk-ruby-1.3

For the release notes, there is XML typically in every guide that seems to serve as an include statement here:

https://github.com/couchbase/docs/blob/master/Couchbase/products/couchbase/couchbase-sdk-ruby-1.3/releasenotes-metasrc.xml

The XML=>HTML conversion runs here: ssh jenkins@ubu-1701.hq.couchbase.com, you can use Qakey.pem to access it

In ~/docs we recreated a shell script that will Git pull the current docs repo
Then it will do a make publish-push to trigger the XML=>HTML conversion

This make task runs a bunch of Perl scripts that do the conversion as well as includes. I believe all the Perl scripts called by make are under the Publish Then the make task syncs the new HTML with our web server.

Let me know if you need the key for access to this machine, but you should have it as it is the QA key for jenkins.



Regards,

Karen



[RCBC-127] Final Review 1.3 core documentation Created: 06/May/13  Updated: 15/May/13

Status: In Progress
Project: Couchbase Ruby client library
Component/s: docs
Affects Version/s: 1.3.0
Fix Version/s: 1.3.0
Security Level: Public

Type: New Feature Priority: Minor
Reporter: Matt Ingenthron Assignee: Karen Zeller
Resolution: Unresolved Votes: 0
Labels: info-request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
We need a new section in the documentation for the upcoming 1.3.0 release. This should:
- Copy the 1.2 manual
- Remove section 3-9, and instead link to the autodocs for the 1.3.0 client
- Rename section 10 (now section 3) to "Common Patterns"

After this is complete, please pass the ticket to Sergey who will write for review:
- Small section on response handling (tmpfail, bulk loading, timeouts)
- small section on event machine (motivation, where it is, how to get more info)
- small section on transcoders (motivation, where it is, how to use it, how to get more info)

I know this is a bit last minute, so we've tried to keep this scope as small as possible and still effective. Our goal would be to have everything done for publishing by EOD on 7th of May.

Sorry for the last minute notification. It only became clear in the last few days that this should be a 1.3 release given the new functionality.

 Comments   
Comment by Karen Zeller [ 06/May/13 ]
Note to Matt and Sergey:


The part you need from me is partially doable in the next hours:

We need a new section in the documentation for the upcoming 1.3.0 release. This should:
- Copy the 1.2 manual
- Remove section 3-9, …..
- Rename section 10 (now section 3) to "Common Patterns"


Getting this out depends on how quickly Sergey can assemble the raw information/knowledge in the new files.

The other part is if the 1.3 gem ready to run the Rdoc build on ubu-1702. Is it ready now for Rdocs?

In order to copyedit them and get my edits in as well as the Rdoc up EOD tomorrow, I will probably need both the code ready and the raw content ready by 2 PM PST tomorrow.

I will assign the ticket to Sergey as soon as the 1.3 files are set up in the next hour.

Regards,

Karen
Comment by Karen Zeller [ 06/May/13 ]

-Creating new files for 1.3
-Updating link to new Rdoc 1.3 from nav
-Add Ruby 1.3 to LibrarySpec.pm to publish
Comment by Karen Zeller [ 06/May/13 ]
Assigning to Sergey to add content to new files in sections described.

Sergey, the 1.3 XML chapters are in:

docs/Couchbase/products/couchbase/couchbase-sdk-ruby-1.3

Let me know when you have added all your raw content as XML for each of the section. I will copyedit them/reorganize, request information from you if needed and the publish.


Comment by Sergey Avseyev [ 07/May/13 ]
Thank you Karen, I've just uploaded to review site two new code examples, which I'm going to use in new documentation sections: http://review.couchbase.org/26153
Comment by Karen Zeller [ 07/May/13 ]
And don't worry about organizing this clearly for now, just get the raw information and knowledge you have into XML paragraphs and lists.

Comment by Sergey Avseyev [ 07/May/13 ]
EventMachine section: https://github.com/couchbase/docs/pull/211
Transcoders section (depends on previous one, because it is modifying the same file): https://github.com/couchbase/docs/pull/212
Comment by Karen Zeller [ 07/May/13 ]
HI Sergey,

So I edited and overhauled your new content and committed it to Github.

Do you guys have a list of standard reviewers I should send this to?


Also, there were some areas that were unclear:

-For Data Transcoders you say these transcoders can be chosen using the current format API, therefore the patch won't break anything. I believe this means that this is compatible with earlier versions of the Ruby SDK. Correct>

-:forced passes the transcoder explicitly. I believe that means that the operations will transcode automatically, please confirm....

-EventMachine. You say that the Ruby client comes with additional engines. But I think this really means it comes with two engines: a default which is Ruby-thread-friendly , and the one which extends EventMachine

-Final note: where are any release notes?


Changed status to minor as going into reviews then publish soon....
Comment by Matt Ingenthron [ 07/May/13 ]
Thanks for the quick turnaround on this Karen! Again apologies for the scramble.

For ruby, we do not have a current list of standard reviewers. I might recommend myself and James Mauss (he's a Ruby guy to some degree).
Comment by Karen Zeller [ 08/May/13 ]
Karen: run the Rdoc for 1.3.
Comment by Sergey Avseyev [ 08/May/13 ]
I've attached zip archive to announcement email
Comment by Karen Zeller [ 08/May/13 ]
Ok, uploaded and linked: http://www.couchbase.com/autodocs/



[RCBC-78] Need Alternative to Event Loop Created: 27/Aug/12  Updated: 28/Aug/12

Status: Open
Project: Couchbase Ruby client library
Component/s: library
Affects Version/s: 1.0.0, 1.1.0, 1.2.0.z.beta
Fix Version/s: 2.0.0
Security Level: Public

Type: Improvement Priority: Major
Reporter: Karen Zeller Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Production Management (DiptiP), and Customer Support team request that we provide an alternative to the event loop for asynchronous operations, which takes a function/callback as a parameter in the method signature and has an explicit return.

 Comments   
Comment by Matt Ingenthron [ 28/Aug/12 ]
In the future, it'd be good for Product Management(sic) to talk with product management: me. :)

This is not something planned in the short term. Moving to 2.0.



[RCBC-65] Accept only allowed options for the methods Created: 27/Jul/12  Updated: 19/Oct/12

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

Type: Improvement Priority: Minor
Reporter: Sergey Avseyev Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
It might be good to complain using ArgumentError on unsupported or invalid keys in options parameter for ruby API. Currently it is possible to pass any Hash as options and the library will silently pick only documented options ignoring all others. This could lead to some confusion (see RCBC-47) when people will use deprecated options or invalid key types (only symbols allowed)



[RCBC-117] Write the getting started with Ruby on Linux section of the essential guide Created: 04/Feb/13  Updated: 04/Feb/13

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

Type: Task Priority: Major
Reporter: MC Brown Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Write the Getting started with Ruby on Linux (Redhat and Debian) section of the Essentials Guide

Needs to cover:

Installation of the Ruby gem/components and pre-requisites
Writing your first (small) app using Couchbase and Ruby

Submissions should be to MC, either through the couchbase/docs repo, or direct to MC in whatever format suits. Must include both the text and images.



[RCBC-116] Write the Getting Started with Ruby on Mac OS X section of the essentials guide Created: 04/Feb/13  Updated: 04/Feb/13

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

Type: Task Priority: Major
Reporter: MC Brown Assignee: Jasdeep Jaitla
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Write the Getting started with Ruby on Mac OS X section of the Essentials Guide

Needs to cover:

Installation of the Ruby gem/components and pre-requisites
Writing your first (small) app using Couchbase and Ruby

Submissions should be to MC, either through the couchbase/docs repo, or direct to MC in whatever format suits. Must include both the text and images.



[RCBC-115] Writ the GettingStarted with Ruby section of the essentials guides Created: 04/Feb/13  Updated: 04/Feb/13

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

Type: Task Priority: Major
Reporter: MC Brown Assignee: John Zablocki
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Write the Getting started with Ruby on Windows section of the Essentials Guide

Needs to cover:

Installation of the Ruby gem/components and pre-requisites
Writing your first (small) app using Couchbase and Ruby

Submissions should be to MC, either through the couchbase/docs repo, or direct to MC in whatever format suits. Must include both the text and images.



[RCBC-93] Ruby Client does not handle the timeout appropriately Created: 24/Oct/12  Updated: 15/Nov/12

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

Type: Bug Priority: Major
Reporter: Bala Keelapudi Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Ruby client 1.1.1

Attachments: File couch.rb    

 Description   
This is the problem that the customer is encountering
(Ruby code coming up):

Timeout::timeout(2) do
couch_client.get(key)
end

But we are seeing Couchbase::Error::Timeout exceptions being raised. I know the default timeout for the Couchbase client gem is greater than 2 seconds, so I'm wondering: what could cause Couchbase to return a timeout (0x16 error code) before it actually has time to timeout?

The complete ruby source code is attached , Please take a look at it.

------
support's analysis:
 The client is not timing out fast enough it should time out in 2.5 sec or something but instead it's waiting a long time.





[RCBC-75] Provide Consistent Order of Parameters Created: 24/Aug/12  Updated: 02/Jan/13

Status: Open
Project: Couchbase Ruby client library
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.0
Security Level: Public

Type: Improvement Priority: Major
Reporter: Karen Zeller Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Provide consistent, predictable order for method parameters as other SDKS.

 Comments   
Comment by Sergey Avseyev [ 24/Aug/12 ]
Could you extend your query please with examples? Where the API is inconsistent and unpredictable?
Comment by Karen Zeller [ 27/Aug/12 ]
Here is the first example. This may require a fix on the Java side vs. the Ruby side:

http://www.couchbase.com/docs/couchbase-sdk-java-1.0/couchbase-sdk-java-set-add.html#table-couchbase-sdk_java_add

Order is key, expiry, then value

Should be one fairly consistent order across the SDKs.

Will add others as either I or others (customer support) run across them.

Comment by Karen Zeller [ 27/Aug/12 ]
I have reassigned this to Matt so this can be looked at globally post 2.0, and hopefully approached across the SDKs. This is a repeated request I am getting from customer support.



[RCBC-73] Provide Consistent Timeouts Created: 24/Aug/12  Updated: 24/Aug/12

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

Type: Improvement Priority: Major
Reporter: Karen Zeller Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Provides the consistent level of time outs with other SDKs. Provide ability to set timeouts at: 1) connection, 2) authentication, and 3) ops level.



[RCBC-72] Need Consistent Error Handling Created: 24/Aug/12  Updated: 24/Aug/12

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

Type: Improvement Priority: Major
Reporter: Karen Zeller Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Need error handling more consistent with other SDKs (error messages) and more consistent with underlying memcached protocol.



[RCBC-61] Allow response aggregation for multi-keyed operations in asynchronous mode Created: 19/Jul/12  Updated: 19/Jul/12

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

Type: Improvement Priority: Major
Reporter: Sergey Avseyev Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Mult-keyed operations behaves a bit different in async mode, they are yielding responses as far as they received. This is good, but it would be nice to have switch to force library to aggregate all of them.

Example:

Couchbase.bucket.run do |c|
  c.get("foo", "bar", "baz", :aggregate => true) do |results|
    results.each do |res|
       # ...
    end
  end
end



[RCBC-55] Update the getting started to match the Beer sample DB Created: 12/Jul/12  Updated: 12/Jul/12

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

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Once the sample DB has been integrated into the server, update the getting started (both on the web page and in the documentation) to use the sample database.




[RCBC-56] Updated screencast for /develop pages Created: 12/Jul/12  Updated: 12/Jul/12

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

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Create an updated screencast to ship with the new 2.0 developer SDKs



[RCBC-41] Integrate log4r and log interesting events for issue investigation Created: 22/Jun/12  Updated: 08/Feb/13

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

Type: New Feature Priority: Major
Reporter: Sergey Avseyev Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by RCBC-74 Provide Standardized Logging Closed
is duplicated by RCBC-108 Add Couchbase operation logging Closed



[RCBC-122] Option to enable configuration cache on libcouchbase Created: 07/Mar/13  Updated: 06/May/13

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

Type: Improvement Priority: Major
Reporter: Sergey Avseyev Assignee: Matt Ingenthron
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by RCBC-126 support libcouchbase configuration cache Resolved



[RCBC-54] Add a unit/integration test validation of OBSERVE + view stale=false Created: 12/Jul/12  Updated: 08/May/13

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

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Ensure that when a synchronous set is used with the new low-level observe, the index is fully updated when querying with view=false.




[RCBC-21] automatically backoff on TMP_OOM Created: 22/Jan/12  Updated: 08/May/13

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

Type: Improvement Priority: Major
Reporter: Matt Ingenthron Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
When a server's memory is full it may start sending TMP_OOM errors to clients, which should be used by the client to temporarily back off (exponential backoff). This helps in bulk load situations where maybe many clients are loading data to a server which is also trying to flush to disk.

 Comments   
Comment by Matt Ingenthron [ 22/Jan/12 ]
libcouchbase may handle this already. If so, simply close this issue.
Comment by Matt Ingenthron [ 08/May/13 ]
Note we may want this to be optional behavior.



[RCBC-109] Add Observe-methods into Rdoc TOC Created: 10/Jan/13  Updated: 11/Jan/13

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

Type: Improvement Priority: Minor
Reporter: Karen Zeller Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
Hi Sergey,

Can you add an item in the top-level RDoc table of content for the observe-methods in Ruby? A customer just asked about it in Rdoc. In general, the Rdoc is great language reference resource for the SDK, but this item that is hard to find from the first Rdoc page: http://www.couchbase.com/autodocs/couchbase-ruby-client-1.2.0/Couchbase/Bucket.html#observe_and_wait-instance_method



Thanks,

Karen




 Comments   
Comment by Sergey Avseyev [ 11/Jan/13 ]
Do you mean into README file which is rendering when you will navigate to http://www.couchbase.com/autodocs/couchbase-ruby-client-1.2.0?
Comment by Karen Zeller [ 11/Jan/13 ]
What I mean is that "USAGE" navigation box where you can see a list of all the major areas. It would be good to have an "observe" item in that list where you have get, etc....



[RCBC-114] Code sample of Get and Lock in Ruby Created: 28/Jan/13  Updated: 06/May/13

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

Type: New Feature Priority: Minor
Reporter: Karen Zeller Assignee: Sergey Avseyev
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   
One of our users asked for a code example demonstrating Get and Lock in Ruby for the Developer Guide.

 Comments   
Comment by Sergey Avseyev [ 06/May/13 ]
There are examples of get with lock usage in our test suite: https://github.com/couchbase/couchbase-ruby-client/blob/master/test/test_get.rb#L349-L397

Generally it is pretty straightforward, just pass ':lock => true' or with number like ':lock => 14' to the Couchbase::Bucket#get method, and expect that key will be locked on default interval (set by the server) or user defined (14 in this case)
Comment by Karen Zeller [ 06/May/13 ]
Hi,

We will get the same feedback if we use this as an example as we tried with PHP.

PHP also only had assertions from TDD, Unit-testing and we were told customers need an actually application-level usage (how to use within a sample application, not a test suite for the SDK).

You should hold this ticket until someone in the team is able to demonstrate GETL in Ruby within a sample application or a code snippet within an application.


Regards,

Karen




Generated at Sun May 19 12:58:07 CDT 2013 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.