<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 14:17:59 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/si/jira.issueviews:issue-xml/PCBC-153/PCBC-153.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Couchbase</title>
    <link>http://www.couchbase.com/issues</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.4</version>
        <build-number>845</build-number>
        <build-date>26-12-2012</build-date>
    </build-info>

<item>
            <title>[PCBC-153] move flush function to RESTful flush</title>
                <link>http://www.couchbase.com/issues/browse/PCBC-153</link>
                <project id="10049" key="PCBC">Couchbase PHP client library</project>
                        <description>With Couchbase bucket types and memcached bucket types, the RESTful flush should always be used in Couchbase Server.  Thus, the flush() function needs to be connected to the restful flush in libcouchbase:&lt;br/&gt;
&lt;a href=&quot;https://github.com/couchbase/libcouchbase/blob/master/tools/cbc.cc#L947&quot;&gt;https://github.com/couchbase/libcouchbase/blob/master/tools/cbc.cc#L947&lt;/a&gt;</description>
                <environment></environment>
            <key id="21032">PCBC-153</key>
            <summary>move flush function to RESTful flush</summary>
                <type id="4" iconUrl="http://www.couchbase.com/issues/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="2" iconUrl="http://www.couchbase.com/issues/images/icons/priorities/critical.png">Critical</priority>
                    <status id="5" iconUrl="http://www.couchbase.com/issues/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10011">Public</security>
                        <assignee username="trond">Trond Norbye</assignee>
                                <reporter username="ingenthr">Matt Ingenthron</reporter>
                        <labels>
                    </labels>
                <created>Fri, 30 Nov 2012 15:21:54 -0600</created>
                <updated>Tue, 11 Dec 2012 19:55:28 -0600</updated>
                    <resolved>Tue, 4 Dec 2012 12:12:47 -0600</resolved>
                                            <fixVersion>1.1.0</fixVersion>
                                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="45102" author="trond" created="Fri, 30 Nov 2012 15:26:48 -0600"  >Is this really a _blocker_ and something we can&amp;#39;t put in the release notes? I wouldn&amp;#39;t assume a &amp;quot;non-working&amp;quot; flush for the couchbase buckets to be the biggest problem for people in production....</comment>
                    <comment id="45278" author="trond" created="Mon, 3 Dec 2012 16:29:07 -0600"  >&lt;a href=&quot;http://review.couchbase.org/#/c/23014/&quot;&gt;http://review.couchbase.org/#/c/23014/&lt;/a&gt;</comment>
                    <comment id="45363" author="chuyskywalker" created="Tue, 4 Dec 2012 12:24:41 -0600"  >I know this is already resolved, but I&amp;#39;d actually implement our own wrapper to detect &amp;quot;is bucket memcached? ok, flush as normal. else _alldocs, loop, delete(key)&amp;quot;. It wasn&amp;#39;t a big deal to implement, just annoying.</comment>
                    <comment id="45367" author="ingenthr" created="Tue, 4 Dec 2012 12:49:36 -0600"  >Thanks Jeff&lt;br/&gt;
&lt;br/&gt;
Use of _alldocs is not recommended or really supported in Couchbase Server 2.0.  It works okay, but it can&amp;#39;t walk the views in an optimal way and thus churns through disk.&lt;br/&gt;
&lt;br/&gt;
The RESTful flush should be relatively speedy and will definitely be speedy in the long term and safe.</comment>
                    <comment id="45368" author="trond" created="Tue, 4 Dec 2012 12:50:11 -0600"  >The rest way should also work for me cached buckets</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                                                <customfield id="customfield_10010" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                <customfieldname>Flagged</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10010"><![CDATA[Release Note]]></customfieldvalue>
    
                </customfieldvalues>
            </customfield>
                                                                                                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>9491</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                    <customfield id="customfield_10181" key="com.atlassian.jira.ext.charting:timeinstatus">
                <customfieldname>Time In Status</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                </customfields>
    </item>
</channel>
</rss>