<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Sat May 18 22:37:17 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/MB-7381/MB-7381.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>[MB-7381] [2.0.1RN]REST API for flush requires admin credentials while it makes sense to allow it with bucket credentials</title>
                <link>http://www.couchbase.com/issues/browse/MB-7381</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>SUBJ.&lt;br/&gt;
&lt;br/&gt;
Matt convinced me that indeed we did it wrong:&lt;br/&gt;
&lt;br/&gt;
&amp;lt;alkby&amp;gt; I believe 1.7 and 1.6 always demanded admin&lt;br/&gt;
&amp;lt;alkby&amp;gt; and 1.8 too&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; that&amp;#39;s a real problem from a client perspective, since someone using a client is just using a bucket&lt;br/&gt;
&amp;lt;alkby&amp;gt; right but flush is a very destructive operation&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; if buckets are in fact about multitenancy, then the tenant should be able to throw away their contents&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; yep, I know.  :)&lt;br/&gt;
&amp;lt;alkby&amp;gt; for unit tests you set it up for bucket with admin credentials&lt;br/&gt;
&amp;lt;alkby&amp;gt; well, tenant is good argument&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; this means it&amp;#39;s not functionally equivalent to memcached flush though, and that was the whole point of &lt;a href=&quot;http://www.couchbase.com/issues/browse/MB-5170&quot; title=&quot;new bucket flush feature&quot;&gt;&lt;strike&gt;MB-5170&lt;/strike&gt;&lt;/a&gt;&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; that we couldn&amp;#39;t do memcached flush safely, so we&amp;#39;d replace it with RESTful flush&lt;br/&gt;
&amp;lt;alkby&amp;gt; you&amp;#39;re right&lt;br/&gt;
&amp;lt;alkby&amp;gt; lets file a bug and address it asap. Thanks for raising this&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; but if restful flush is different semantically (you can flush this only with super creds)&lt;br/&gt;
&amp;lt;ingenthr&amp;gt; okay, will do, thanks&lt;br/&gt;
&amp;lt;alkby&amp;gt; I&amp;#39;ll file bug&lt;br/&gt;
&lt;br/&gt;
</description>
                <environment></environment>
            <key id="21211">MB-7381</key>
            <summary>[2.0.1RN]REST API for flush requires admin credentials while it makes sense to allow it with bucket credentials</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="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="Aliaksey Artamonau">Aliaksey Artamonau</assignee>
                                <reporter username="alkondratenko">Aleksey Kondratenko</reporter>
                        <labels>
                    </labels>
                <created>Fri, 7 Dec 2012 21:05:12 -0600</created>
                <updated>Mon, 14 Jan 2013 18:51:06 -0600</updated>
                    <resolved>Mon, 14 Jan 2013 18:27:51 -0600</resolved>
                            <version>2.0</version>
                                <fixVersion>2.0.1</fixVersion>
                                <component>ns_server</component>
                                <votes>0</votes>
                        <watches>4</watches>
                                                    <comments>
                    <comment id="45733" author="farshid" created="Mon, 10 Dec 2012 13:37:15 -0600"  >per bug scrub - deferring to 2.1</comment>
                    <comment id="45743" author="ingenthr" created="Mon, 10 Dec 2012 13:56:56 -0600"  >2.1?  So we&amp;#39;ll leave this broken for the remainder of 2.0.x?  There&amp;#39;s no API breakage in fixing it in 2.0.x that I&amp;#39;m aware of.</comment>
                    <comment id="45744" author="alkondratenko" created="Mon, 10 Dec 2012 14:08:37 -0600"  >IMHO clearly not 2.0.1 but good fit for 2.0.2</comment>
                    <comment id="46471" author="ingenthr" created="Fri, 21 Dec 2012 02:32:13 -0600"  >Note that there was a request around this area and a workaround mentioned for the Java client mentioned here:&lt;br/&gt;
&lt;br/&gt;
&lt;a href=&quot;http://www.couchbase.com/forums/thread/flush-gui-works-not-spy-memcached&quot;&gt;http://www.couchbase.com/forums/thread/flush-gui-works-not-spy-memcached&lt;/a&gt;</comment>
                    <comment id="47569" author="dipti" created="Thu, 10 Jan 2013 17:40:10 -0600"  >Karen, Note that we will need a documentation change for this bug in 2.0.1. &lt;br/&gt;
&lt;br/&gt;
</comment>
                    <comment id="47623" author="kzeller" created="Fri, 11 Jan 2013 16:23:34 -0600"  >Nominating for 2.0.1 RN</comment>
                    <comment id="47743" author="alkondratenko" created="Mon, 14 Jan 2013 17:41:07 -0600"  >Dipti said it&amp;#39;s a good to have for 2.0.1, please help me with backporting.</comment>
                    <comment id="47746" author="Aliaksey Artamonau" created="Mon, 14 Jan 2013 18:27:51 -0600"  >&lt;a href=&quot;http://review.couchbase.org/23930&quot;&gt;http://review.couchbase.org/23930&lt;/a&gt;&lt;br/&gt;
Merged to 2.0.1.</comment>
                    <comment id="47751" author="kzeller" created="Mon, 14 Jan 2013 18:50:41 -0600"  >Note: Add to 2.0.1 Release Notes</comment>
                </comments>
                <issuelinks>
                        <issuelinktype id="10000">
                <name>Dependency</name>
                                                <inwardlinks description="blocks">
                            <issuelink>
            <issuekey id="21212">JCBC-173</issuekey>
        </issuelink>
                    </inwardlinks>
                            </issuelinktype>
                    </issuelinks>
                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                        <customfield id="customfield_10180" key="com.atlassian.jira.ext.charting:firstresponsedate">
                <customfieldname>Date of First Response</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>Mon, 10 Dec 2012 13:37:15 -0600</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                    <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>3448</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>