<!--
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Wed May 22 23:41:00 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.couchbase.com/issues/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+JCBC+AND+status+%3D+%22In+Progress%22+ORDER+BY+priority+DESC&tempMax=1000&field=key&field=summary
-->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
<?xml-stylesheet href="http://www.couchbase.com/issues/styles/jiraxml2html.xsl" type="text/xsl"?>
-->
<rss version="0.92">
    <channel>
        <title>Couchbase</title>
        <link>http://www.couchbase.com/issues/secure/IssueNavigator.jspa?reset=true&amp;jqlQuery=project+%3D+JCBC+AND+status+%3D+%22In+Progress%22+ORDER+BY+priority+DESC</link>
        <description>An XML representation of a search request</description>
                <language>en-us</language>
                        <issue start="0" end="7" total="7"/>
                <build-info>
            <version>5.2.4</version>
            <build-number>845</build-number>
            <build-date>26-12-2012</build-date>
        </build-info>
<item>
            <title>[JCBC-276] Client does not detect silently dying Streaming Node</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-276</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>When connected to the EPT/streaming node and the node is &amp;quot;frozen&amp;quot; or dies silently otherwise (doesn&amp;#39;t force the closing of the chunked socket), the connection stays established.&lt;br/&gt;
&lt;br/&gt;
This can easily be reproduced outside of the client by connecting the browser to the streaming URL and then freezing a VM. The browser will still &amp;quot;spin&amp;quot; and wait for new chunks to come up.&lt;br/&gt;
&lt;br/&gt;
The proposed solution is to have a netty handler in place that raises a exception when there is not traffic for N number of seconds (like 30) over the streaming connection. After this is detected, we have two possibilities:&lt;br/&gt;
&lt;br/&gt;
- reconnect completely, but this involves lots of overhead every 30 seconds.&lt;br/&gt;
- send a HTTP HEAD packet and only if this doesnt work out reconnect. This  means in the normal case we only have a HTTP HEAD request sent every 30 seconds, not much overhead.&lt;br/&gt;
If this fails, we then trigger the reconfigure.&lt;br/&gt;
&lt;br/&gt;
Netty has a ReadTimeoutHandler to help with this. My POC already kinda works, I just need to find a way to properly distinguish the HEAD response on the ResponseHandler from regular chunks that arrive from the same channel.</description>
                <environment></environment>
            <key id="23312">JCBC-276</key>
            <summary>Client does not detect silently dying Streaming Node</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="2" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/critical.png">Critical</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="daschl">Michael Nitschinger</assignee>
                                <reporter username="daschl">Michael Nitschinger</reporter>
                        <labels>
                    </labels>
                <created>Wed, 20 Mar 2013 07:21:07 -0500</created>
                <updated>Mon, 20 May 2013 14:30:42 -0500</updated>
                                    <version>1.1.0</version>
                <version>1.1.1</version>
                <version>1.1.2</version>
                <version>1.1.3</version>
                <version>1.1.4</version>
                                <fixVersion>1.1.7</fixVersion>
                                <component>library</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="53178" author="ingenthr" created="Wed, 20 Mar 2013 12:30:07 -0500"  >I had fixed this with couchbase buckets and we test for this in SDKQE.  Is this possibly isolated to memcached buckets.</comment>
                    <comment id="53227" author="daschl" created="Thu, 21 Mar 2013 01:06:13 -0500"  >Actually, this has been discovered while using Couchbase buckets. Let&amp;#39;s chat about this, but I think thats a different issue and not related to it.</comment>
                    <comment id="53228" author="ingenthr" created="Thu, 21 Mar 2013 01:39:43 -0500"  >Sure, the solution previously was to have that threshold if we were getting unexpected failures.  Once we pass that threshold, we&amp;#39;d try to re-subscribe.  &lt;br/&gt;
&lt;br/&gt;
I&amp;#39;m not opposed to a heartbeat, but I don&amp;#39;t think the HTTP HEAD is good, since the mochiweb erlang implementation is effectively the same as a GET.  I&amp;#39;ll reach you and chat through it.</comment>
                    <comment id="53243" author="daschl" created="Thu, 21 Mar 2013 09:14:48 -0500"  >Okay after talking this through with Matt, I reran the script to see if the proposed solution (increasing ops/s) fixed the problem.&lt;br/&gt;
&lt;br/&gt;
Interestingly, it turns out when doing set/get&amp;#39;s it never hits our anticipated codepath but instead the get operations just time out, the threshold never gets increased and nothing happens. This is something we need to reinvestigate.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                            <customfield id="customfield_10284" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                <customfieldname>Planned End</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Wed, 20 Mar 2013 12:00:00 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10283" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                <customfieldname>Planned Start</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Wed, 20 Mar 2013 12:00:00 -0500</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>10164</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>

<item>
            <title>[JCBC-229] Find a way to proper test JCBC-227</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-229</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>The issue fixed in jcbc-227 needs proper testing. Can you please add tests for this either as a unit test, or integrate it into sdkd? I&amp;#39;m not sure where it fits - what do you think?</description>
                <environment></environment>
            <key id="22225">JCBC-229</key>
            <summary>Find a way to proper test JCBC-227</summary>
                <type id="3" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/task.png">Task</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="deeptida">Deepti Dawar</assignee>
                                <reporter username="daschl">Michael Nitschinger</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Feb 2013 02:53:20 -0600</created>
                <updated>Mon, 25 Feb 2013 05:12:00 -0600</updated>
                                    <version>1.1.2</version>
                                <fixVersion>.next</fixVersion>
                                <component>library</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="49373" author="deeptida" created="Fri, 1 Feb 2013 05:01:38 -0600"  >Alright, I can add unit/integration test for the same.&lt;br/&gt;
</comment>
                    <comment id="50107" author="deeptida" created="Mon, 11 Feb 2013 17:14:11 -0600"  >&lt;a href=&quot;http://review.couchbase.org/#/c/24520/&quot;&gt;http://review.couchbase.org/#/c/24520/&lt;/a&gt;</comment>
                    <comment id="50146" author="daschl" created="Tue, 12 Feb 2013 00:09:44 -0600"  >Please only close once the change has been merged in, thanks.</comment>
                    <comment id="50400" author="deeptida" created="Thu, 14 Feb 2013 04:53:43 -0600"  >&lt;a href=&quot;http://review.couchbase.org/#/c/24520/6&quot;&gt;http://review.couchbase.org/#/c/24520/6&lt;/a&gt;</comment>
                </comments>
                <issuelinks>
                        <issuelinktype id="10000">
                <name>Dependency</name>
                                <outwardlinks description="depends on">
                                    </outwardlinks>
                                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>2945</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>

<item>
            <title>[JCBC-303] javadoc builds must include spymemcached</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-303</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>Current javadoc build process does not include the spymemcached docs, which were included in previous releases.  The documentation:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;a href=&quot;http://hub.internal.couchbase.com/confluence/display/techpubs/Using+Existing+Docs+System+%28WIP%29&quot;&gt;http://hub.internal.couchbase.com/confluence/display/techpubs/Using+Existing+Docs+System+%28WIP%29&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
does not mention how to include, nor is there evidence of how it was done before.&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Need to have:&lt;br/&gt;
&lt;br/&gt;
* a process that includes correct third-party documentation, when required.&lt;br/&gt;
&lt;br/&gt;
* one that is not tied to a particular host&lt;br/&gt;
&lt;br/&gt;
* is fully documented</description>
                <environment></environment>
            <key id="24250">JCBC-303</key>
            <summary>javadoc builds must include spymemcached</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="plabee">Phil Labee</assignee>
                                <reporter username="plabee">Phil Labee</reporter>
                        <labels>
                    </labels>
                <created>Tue, 14 May 2013 12:41:40 -0500</created>
                <updated>Wed, 15 May 2013 11:21:36 -0500</updated>
                                    <version>1.1.6</version>
                                                <component>infrastructure</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="58349" author="plabee" created="Wed, 15 May 2013 11:15:56 -0500"  >I modified the couchbase-java-client/build.xml file to also use the source files under &lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;../spymemcached/src/main/java/&lt;br/&gt;
&lt;br/&gt;
for generating javadocs, but I&amp;#39;m getting errors:&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;package org.apache.log4j does not exist&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;package org.springframework.beans.factory does not exist&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;br/&gt;
so it looks like a classpath issue.</comment>
                    <comment id="58351" author="daschl" created="Wed, 15 May 2013 11:21:36 -0500"  >Hi Phil,&lt;br/&gt;
&lt;br/&gt;
normally log4j and spring beans are configured as &amp;quot;provided&amp;quot;, so you should not need them during runtime in spy. maybe just run &amp;quot;ant jar&amp;quot; once in the directory so it fetches the dependencies in the right directories?&lt;br/&gt;
</comment>
                </comments>
                <issuelinks>
                        <issuelinktype id="10001">
                <name>Duplicate</name>
                                <outwardlinks description="duplicates">
                            <issuelink>
            <issuekey id="24028">JCBC-293</issuekey>
        </issuelink>
                    </outwardlinks>
                                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>11223</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>

<item>
            <title>[JCBC-189] Views having odd timeout issues on some clusters</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-189</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>We&amp;#39;re seeing really strange timeout issues which seem to affect only this specific cluster and only in terms of views. We&amp;#39;ve re-installed this cluster time and time again, and we&amp;#39;ve had similar configurations run successfully as well.&lt;br/&gt;
&lt;br/&gt;
More details in comment..</description>
                <environment></environment>
            <key id="21413">JCBC-189</key>
            <summary>Views having odd timeout issues on some clusters</summary>
                <type id="1" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/major.png">Major</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="daschl">Michael Nitschinger</assignee>
                                <reporter username="mnunberg">Mark Nunberg</reporter>
                        <labels>
                    </labels>
                <created>Tue, 18 Dec 2012 21:44:37 -0600</created>
                <updated>Mon, 20 May 2013 14:30:46 -0500</updated>
                                    <version>1.1.0</version>
                                <fixVersion>1.1.7</fixVersion>
                                <component>library</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="46263" author="mnunberg" created="Tue, 18 Dec 2012 21:55:02 -0600"  >Just try to do this with a simple java script (i.e. connect and query the view)</comment>
                    <comment id="46401" author="deeptida" created="Thu, 20 Dec 2012 04:20:13 -0600"  >This issue persists when the view retrieval is ran from standalone java program as well.&lt;br/&gt;
I tried this on both the VMs - 10.3.3.203, 10.3.3.209.</comment>
                    <comment id="46403" author="deeptida" created="Thu, 20 Dec 2012 05:35:07 -0600"  >Its working fine for server deployed on localhost.</comment>
                    <comment id="46915" author="ingenthr" created="Wed, 2 Jan 2013 16:51:07 -0600"  >Michael: found out today that this is a large issue for SDKQE.  Can you have a quick look at this in the next day?  You may find the underlying issue.</comment>
                    <comment id="46971" author="daschl" created="Thu, 3 Jan 2013 09:57:11 -0600"  >Please pass me the script as commented and then (or if you can&amp;#39;t) please assign it back to me! Thanks</comment>
                    <comment id="48045" author="daschl" created="Fri, 18 Jan 2013 02:39:59 -0600"  >According to the posted logs, it looks like debugging was not turned on. Can you please run this again with debugging turned on? To get the full logs to STDOUT, use this before initializing the CouchbaseClient in The App:&lt;br/&gt;
&lt;br/&gt;
&amp;#xA0; &amp;#xA0; &amp;#xA0; // Tell spy to use the SunLogger&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;Properties systemProperties = System.getProperties();&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;systemProperties.put(&amp;quot;net.spy.log.LoggerImpl&amp;quot;, &amp;quot;net.spy.memcached.compat.log.SunLogger&amp;quot;);&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;System.setProperties(systemProperties);&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;Logger.getLogger(&amp;quot;com.couchbase.client&amp;quot;).setLevel(Level.FINEST);&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;//get the top Logger&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;Logger topLogger = java.util.logging.Logger.getLogger(&amp;quot;&amp;quot;);&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;// Handler for console (reuse it if it already exists)&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;Handler consoleHandler = null;&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;//see if there is already a console handler&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;for (Handler handler : topLogger.getHandlers()) {&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;if (handler instanceof ConsoleHandler) {&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;//found the console handler&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;consoleHandler = handler;&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;break;&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;}&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;}&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;if (consoleHandler == null) {&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;//there was no console handler found, create a new one&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;consoleHandler = new ConsoleHandler();&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;topLogger.addHandler(consoleHandler);&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;}&lt;br/&gt;
&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;//set the console handler to fine:&lt;br/&gt;
&amp;nbsp;&amp;#xA0; &amp;#xA0; &amp;#xA0; &amp;#xA0;consoleHandler.setLevel(java.util.logging.Level.FINEST);&lt;br/&gt;
&lt;br/&gt;
&lt;br/&gt;
Would be great if we can get all the output so we can investigate where the timeouts come from. I&amp;#39;m sure with a debug log it will be much easier. Thanks!</comment>
                    <comment id="48453" author="mnunberg" created="Wed, 23 Jan 2013 20:28:29 -0600"  >So this bug isn&amp;#39;t such an &amp;quot;unknown&amp;quot; anymore, and has exposed itself in 1.1.0 as well as 1.1.1 and isn&amp;#39;t limited to particular clusters - (it just seems that some clusters are more likely than others to trigger this bug).&lt;br/&gt;
&lt;br/&gt;
However this still needs a lot of care and analysis</comment>
                    <comment id="49377" author="daschl" created="Fri, 1 Feb 2013 06:26:32 -0600"  >This is &amp;quot;kinda&amp;quot; blocker.</comment>
                </comments>
                <issuelinks>
                        <issuelinktype id="10000">
                <name>Dependency</name>
                                <outwardlinks description="depends on">
                            <issuelink>
            <issuekey id="22230">MB-7661</issuekey>
        </issuelink>
                    </outwardlinks>
                                                <inwardlinks description="blocks">
                            <issuelink>
            <issuekey id="21220">JCBC-176</issuekey>
        </issuelink>
                    </inwardlinks>
                            </issuelinktype>
                    </issuelinks>
                <attachments>
                    <attachment id="16112" name="failover-debug.args" size="435" author="deeptida" created="Fri, 4 Jan 2013 02:44:13 -0600" />
                    <attachment id="16032" name="fo-dbg.log.txt" size="20447" author="mnunberg" created="Tue, 18 Dec 2012 21:55:56 -0600" />
                    <attachment id="16111" name="vm-4nodes-2.ini" size="179" author="deeptida" created="Fri, 4 Jan 2013 02:44:13 -0600" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>8583</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>

<item>
            <title>[JCBC-244] Sample Application : fix the welcome file and gitignore</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-244</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>1- the Welcome auto redirect in Jetty does not work correctly.&lt;br/&gt;
2- Update the gitignore to handle IDE and OS</description>
                <environment></environment>
            <key id="22631">JCBC-244</key>
            <summary>Sample Application : fix the welcome file and gitignore</summary>
                <type id="3" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/task.png">Task</type>
                                <priority id="4" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/minor.png">Minor</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="tgrall">Tug Grall</assignee>
                                <reporter username="tgrall">Tug Grall</reporter>
                        <labels>
                    </labels>
                <created>Tue, 12 Feb 2013 03:34:33 -0600</created>
                <updated>Thu, 2 May 2013 16:33:23 -0500</updated>
                                    <version>1.1.2</version>
                                                <component>docs</component>
                                <votes>0</votes>
                        <watches>2</watches>
                                                    <comments>
                    <comment id="53502" author="daschl" created="Tue, 26 Mar 2013 07:05:13 -0500"  >Hey tug, is this still ongoing?</comment>
                    <comment id="55036" author="daschl" created="Mon, 15 Apr 2013 02:10:37 -0500"  >Tug, did you fix this recently?</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>10829</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>

<item>
            <title>[JCBC-161] Remove Duplication in Observe checks</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-161</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>The fix for &lt;a href=&quot;http://www.couchbase.com/issues/browse/JCBC-148&quot; title=&quot;Issue with Observe API Persist.TWO and 1 dead node: Time Out when doing set operation&quot;&gt;&lt;strike&gt;JCBC-148&lt;/strike&gt;&lt;/a&gt; works, but it checks against all nodes in the cluster. If you have a larger cluster, you have much more nodes than there could be assigned to a specific key. As an enhancement, the code in checkConfigAgainstPersistence should check against the nodes for the given key, not for everything.</description>
                <environment></environment>
            <key id="21070">JCBC-161</key>
            <summary>Remove Duplication in Observe checks</summary>
                <type id="4" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="4" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/minor.png">Minor</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="daschl">Michael Nitschinger</assignee>
                                <reporter username="daschl">Michael Nitschinger</reporter>
                        <labels>
                    </labels>
                <created>Mon, 3 Dec 2012 03:33:46 -0600</created>
                <updated>Mon, 20 May 2013 14:30:47 -0500</updated>
                                    <version>1.1.0</version>
                                <fixVersion>1.1.7</fixVersion>
                                <component>library</component>
                                <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="57998" author="daschl" created="Mon, 13 May 2013 05:17:40 -0500"  >&lt;a href=&quot;http://review.couchbase.org/#/c/26261/&quot;&gt;http://review.couchbase.org/#/c/26261/&lt;/a&gt;</comment>
                    <comment id="58000" author="daschl" created="Mon, 13 May 2013 05:26:53 -0500"  >Note that the new mechanism was implemented in a different changeset, and by now we had both in place behind one after another. since the other one was more accurate, the general one will be removed in favor of the other one.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>27</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                <customfield id="customfield_10080" key="com.pyxis.greenhopper.jira:gh-sprint">
                <customfieldname>Sprint</customfieldname>
                <customfieldvalues>
                        <customfieldvalue>13</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                    </customfields>
    </item>

<item>
            <title>[JCBC-76] Replica read command</title>
                <link>http://www.couchbase.com/issues/browse/JCBC-76</link>
                <project id="10080" key="JCBC">Couchbase Java Client</project>
                        <description>Implement a simple replica read command</description>
                <environment></environment>
            <key id="18333">JCBC-76</key>
            <summary>Replica read command</summary>
                <type id="4" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="4" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/minor.png">Minor</priority>
                    <status id="3" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/inprogress.png">In Progress</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10011">Public</security>
                        <assignee username="daschl">Michael Nitschinger</assignee>
                                <reporter username="ingenthr">Matt Ingenthron</reporter>
                        <labels>
                    </labels>
                <created>Thu, 12 Jul 2012 00:13:11 -0500</created>
                <updated>Mon, 20 May 2013 14:30:49 -0500</updated>
                                                    <fixVersion>1.1.7</fixVersion>
                                <component>library</component>
                                <votes>0</votes>
                        <watches>1</watches>
                                                    <comments>
                    <comment id="37289" author="ingenthr" created="Wed, 29 Aug 2012 18:56:22 -0500"  >See &lt;a href=&quot;http://www.couchbase.com/wiki/display/couchbase/Replica+Read&quot;&gt;http://www.couchbase.com/wiki/display/couchbase/Replica+Read&lt;/a&gt; for details on implementation.</comment>
                    <comment id="39078" author="rags" created="Fri, 14 Sep 2012 19:41:38 -0500"  >This will be experimental functionality for 1.1</comment>
                    <comment id="49165" author="daschl" created="Thu, 31 Jan 2013 09:16:15 -0600"  >Moving to .next until it is decided if this will make it into 1.2 or not.</comment>
                    <comment id="50396" author="ingenthr" created="Thu, 14 Feb 2013 02:13:17 -0600"  >Michael: this has come up again recently so if possible we&amp;#39;d like to get it in a build for testing soon and see about adding it as experimental, if not supported, in 1.1.3.</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                                                                                                                    <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>8823</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>