<!-- 
RSS generated by JIRA (5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9) at Tue May 21 21:09:12 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-6942/MB-6942.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-6942] Spatial views return debug information and wrong number of total_rows</title>
                <link>http://www.couchbase.com/issues/browse/MB-6942</link>
                <project id="10010" key="MB">Couchbase Server</project>
                        <description>When you query a spatial view, e.g:&lt;br/&gt;
&lt;br/&gt;
curl -X GET &amp;#39;&lt;a href=&quot;http://cato:9500/default/_design/dev_foo/_spatial/bar&amp;#39;&quot;&gt;http://cato:9500/default/_design/dev_foo/_spatial/bar&amp;amp;#39;&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
The result contain a &amp;quot;node&amp;quot; key, which should only be the case when you use debug=true.&lt;br/&gt;
&lt;br/&gt;
The results also always return total_rows=0 (not sure if that ever worked :)</description>
                <environment>Current checkout</environment>
            <key id="20285">MB-6942</key>
            <summary>Spatial views return debug information and wrong number of total_rows</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="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="vmx">Volker Mische</assignee>
                                <reporter username="vmx">Volker Mische</reporter>
                        <labels>
                    </labels>
                <created>Wed, 17 Oct 2012 10:31:24 -0500</created>
                <updated>Thu, 15 Nov 2012 13:17:02 -0600</updated>
                    <resolved>Fri, 19 Oct 2012 13:33:45 -0500</resolved>
                            <version>2.0-beta</version>
                                <fixVersion>2.0-beta-2</fixVersion>
                                <component>view-engine</component>
                                <votes>0</votes>
                        <watches>0</watches>
                                                    <comments>
                    <comment id="41645" author="vmx" created="Wed, 17 Oct 2012 11:31:47 -0500"  >Spatial views don&amp;#39;t return a total_rows property, but it is needed for the view merging. Hence the output it simply &amp;quot;0&amp;quot;.</comment>
                    <comment id="41650" author="vmx" created="Wed, 17 Oct 2012 11:46:46 -0500"  >Here&amp;#39;s a fix: &lt;a href=&quot;http://review.couchbase.org/21717&quot;&gt;http://review.couchbase.org/21717&lt;/a&gt;</comment>
                    <comment id="43837" author="kzeller" created="Mon, 12 Nov 2012 15:44:28 -0600"  >Added to RN: For geo/spatial indexes, which are experimental &lt;br/&gt;
features in Couchbase 2.0, we had &lt;br/&gt;
returned the wrong number of rows in a result set &lt;br/&gt;
by including the node key. We now exclude this key.</comment>
                    <comment id="43851" author="vmx" created="Mon, 12 Nov 2012 16:54:41 -0600"  >This is not fully correct. The &amp;quot;node&amp;quot; key is separate from the wrong number of &amp;quot;total_rows&amp;quot;. Let me explain it a bit.&lt;br/&gt;
The &amp;quot;node&amp;quot; key was a bug and is now fully gone.&lt;br/&gt;
The &amp;quot;total_rows&amp;quot; is always 0 for spatial views. This is still the case and won&amp;#39;t be changed in the near future.</comment>
                    <comment id="44123" author="kzeller" created="Thu, 15 Nov 2012 13:17:02 -0600"  >For geo/spatial indexes, which are experimental &lt;br/&gt;
features in Couchbase 2.0, we had &lt;br/&gt;
erroneously returned a &amp;#39;node&amp;#39; key in the result set which is &lt;br/&gt;
debug information. This is now fixed.</comment>
                </comments>
                    <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, 12 Nov 2012 15:44:28 -0600</customfieldvalue>

                </customfieldvalues>
            </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10081" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Rank</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>3729</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                                                                                                            <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                <customfieldname>Sprint Priority</customfieldname>
                <customfieldvalues>
                    <customfieldvalue>1.0</customfieldvalue>
                </customfieldvalues>
            </customfield>
                                            <customfield id="customfield_10052" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                <customfieldname>Sprint Status</customfieldname>
                <customfieldvalues>
                        <customfieldvalue key="10027"><![CDATA[Current Sprint]]></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>