<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 02:59:48 UTC 2024

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 append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-2381] Cannot use compound of 2d and multikey index</title>
                <link>https://jira.mongodb.org/browse/SERVER-2381</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;2 examples with unexpected results:&lt;/p&gt;

&lt;p&gt;db.test.insert({ &lt;br/&gt;
        point:&lt;span class=&quot;error&quot;&gt;&amp;#91;1,10&amp;#93;&lt;/span&gt;, &lt;br/&gt;
        tags:[ &lt;br/&gt;
                &lt;/p&gt;
{k:&apos;key&apos;,v:&apos;value&apos;}
&lt;p&gt;, &lt;/p&gt;
                {k:&apos;key2&apos;,v:123} 
&lt;p&gt;        ] &lt;br/&gt;
}) &lt;/p&gt;

&lt;p&gt;db.test.insert({ &lt;br/&gt;
        point:&lt;span class=&quot;error&quot;&gt;&amp;#91;1,10&amp;#93;&lt;/span&gt;, &lt;br/&gt;
        tags:&lt;/p&gt;
{k:&apos;key&apos;,v:&apos;value&apos;}
&lt;p&gt; &lt;br/&gt;
}) &lt;/p&gt;

&lt;p&gt;db.test.ensureIndex(&lt;/p&gt;
{point:&quot;2d&quot;,&quot;tags.k&quot;:1,&quot;tags.v&quot;:1}
&lt;p&gt;) &lt;br/&gt;
db.test.find({ &lt;br/&gt;
        point:{&quot;$within&quot;:{&quot;$box&quot;:[&lt;span class=&quot;error&quot;&gt;&amp;#91;0,0&amp;#93;&lt;/span&gt;,&lt;span class=&quot;error&quot;&gt;&amp;#91;12,12&amp;#93;&lt;/span&gt;]}}, &lt;br/&gt;
        &quot;tags.k&quot;:&quot;key&quot; &lt;br/&gt;
}) &lt;/p&gt;

&lt;p&gt;Only 1 result:&lt;br/&gt;
{ &quot;_id&quot; : ObjectId(&quot;4d373f753ffe71e78a71bfc0&quot;), &quot;point&quot; : [ 1, 10 ], &lt;br/&gt;
&quot;tags&quot; : &lt;/p&gt;
{ &quot;k&quot; : &quot;key&quot;, &quot;v&quot; : &quot;value&quot; }
&lt;p&gt; }&lt;/p&gt;


&lt;p&gt;2) &lt;br/&gt;
db.test.drop() &lt;br/&gt;
db.test.insert({p:&lt;span class=&quot;error&quot;&gt;&amp;#91;1112,3473&amp;#93;&lt;/span&gt;,t:[&lt;/p&gt;
{k:&apos;a&apos;,v:&apos;b&apos;}
&lt;p&gt;,&lt;/p&gt;
{k:&apos;c&apos;,v:&apos;d&apos;}
&lt;p&gt;]}) &lt;br/&gt;
db.test.ensureIndex(&lt;/p&gt;
{p:&apos;2d&apos;,&apos;t.k&apos;:1,&apos;t.v&apos;:1}
&lt;p&gt;,&lt;/p&gt;
{min:0,max:10000}
&lt;p&gt;) &lt;br/&gt;
db.test.find(&lt;/p&gt;
{p:[1112,3473],&apos;t.k&apos;:&apos;a&apos;}
&lt;p&gt;) &lt;br/&gt;
No result.&lt;/p&gt;


&lt;p&gt;Some discussion here: &lt;a href=&quot;http://groups.google.com/group/mongodb-user/browse_thread/thread/8fa375ba78081b2c/fd9967f89ff758da&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://groups.google.com/group/mongodb-user/browse_thread/thread/8fa375ba78081b2c/fd9967f89ff758da&lt;/a&gt;&lt;/p&gt;</description>
                <environment>Debian Linux, x64</environment>
        <key id="14259">SERVER-2381</key>
            <summary>Cannot use compound of 2d and multikey index</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="greg_10gen">Greg Studer</assignee>
                                    <reporter username="andi">Andreas Kalsch</reporter>
                        <labels>
                    </labels>
                <created>Thu, 20 Jan 2011 00:43:41 +0000</created>
                <updated>Tue, 12 Jul 2016 00:19:59 +0000</updated>
                            <resolved>Thu, 21 Apr 2011 21:25:09 +0000</resolved>
                                    <version>1.6.5</version>
                    <version>1.7.4</version>
                                    <fixVersion>1.8.0</fixVersion>
                                    <component>Geo</component>
                    <component>Index Maintenance</component>
                                        <votes>8</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="25396" author="greg_10gen" created="Mon, 7 Mar 2011 14:37:08 +0000"  >&lt;p&gt;Unfortunately breaking up your elements won&apos;t speed things up (and may slow things down), as the lookup logic will effectively still be geo-filter &lt;b&gt;then&lt;/b&gt; t-filter individually.  The benefit of additional criteria in a geo-index is that the specified fields get added to the index keys themselves (including multi-key fields, as was fixed earlier), making the filtering faster as there is no additional object lookup required (as in the case with covered indices).&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialIndexing-CompoundIndexes&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.mongodb.org/display/DOCS/Geospatial+Indexing#GeospatialIndexing-CompoundIndexes&lt;/a&gt; mentions this, though not as clearly as one might hope.&lt;/p&gt;

&lt;p&gt;Understand you&apos;re looking for a general multi-d indexing solution, but it&apos;s not quite there yet.&lt;/p&gt;</comment>
                            <comment id="25326" author="andi" created="Sat, 5 Mar 2011 04:07:46 +0000"  >&lt;p&gt;Now I will create several documents to index one document, by creating one for every array element and not using arrays any more. In this case I need to add an additional grouping to guarantee unique results.&lt;/p&gt;

&lt;p&gt;db.bri.drop()&lt;/p&gt;

&lt;p&gt;db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500582142917&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(582142917),
		&quot;c&quot; : [
			34378,
			21334
		],
		&quot;t&quot; : 4294968392
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500582142917&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(582142917),
		&quot;c&quot; : [
			34378,
			21334
		],
		&quot;t&quot; : 4715874093102
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			315540509818880
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			794568949810
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			2104533975531
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			592705486860
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			803158886206
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			4294967999
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : 
			1327144898739
	}
&lt;p&gt;)&lt;br/&gt;
db&lt;span class=&quot;error&quot;&gt;&amp;#91;&amp;#39;bri&amp;#39;&amp;#93;&lt;/span&gt;.ensureIndex(&lt;/p&gt;
{ c: &apos;2d&apos;, t: 1 }
&lt;p&gt;, &lt;/p&gt;
{ min: 0, max: 66000 }
&lt;p&gt;)&lt;br/&gt;
db.bri.find({c:{$within:{$box:[&lt;span class=&quot;error&quot;&gt;&amp;#91;34373, 21334&amp;#93;&lt;/span&gt;,&lt;span class=&quot;error&quot;&gt;&amp;#91;34378, 21339&amp;#93;&lt;/span&gt;]}}, t:{ &quot;$gte&quot; : 201863462912, &quot;$lte&quot; : 206158430207 }}).limit(200).toArray()&lt;/p&gt;

&lt;p&gt;I am right that, in this case (WITHOUT the multikey design), the full index will be used? (Else, it would make no sense to combine 2d + 1.)&lt;/p&gt;</comment>
                            <comment id="25293" author="greg_10gen" created="Fri, 4 Mar 2011 23:15:29 +0000"  >&lt;p&gt;Think the operator you&apos;re looking for is $elemMatch, it supports the array-search semantics you&apos;re looking for.  As far as efficiency, the additional criteria will work, but won&apos;t be index-accelerated, which may still be fast enough for what you need if your additional t-arrays do not grow too large.&lt;/p&gt;</comment>
                            <comment id="25143" author="andi" created="Thu, 3 Mar 2011 12:35:57 +0000"  >&lt;p&gt;&quot;so if an element is &amp;gt; 201 billion and &lt;b&gt;another&lt;/b&gt; element is &amp;lt; 201 billion, it is added&quot;&lt;br/&gt;
That&apos;s the point and it seems awkward to me that it is interpreted this way. I would expect checks always for &lt;b&gt;one&lt;/b&gt; element. In this case, I need to remove the multikey design.&lt;/p&gt;

&lt;p&gt;&quot;If there are additional criteria, the geo-index can&apos;t be used for that query (though you can create an additional regular index to quickly look up exact values). It&apos;s a little bit awkward, but the geo-indexes store additional details differently (and in a way not really very suitable for further filtering).&quot;&lt;br/&gt;
I am waiting for nd (at least 3d) indexing ( &lt;a href=&quot;http://jira.mongodb.org/browse/SERVER-691&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;http://jira.mongodb.org/browse/SERVER-691&lt;/a&gt; ). This would allow much more flexibility. So there is no scalable way to search for 2d (big box) + 1d range in 1 query?&lt;/p&gt;</comment>
                            <comment id="24915" author="greg_10gen" created="Tue, 1 Mar 2011 00:42:07 +0000"  >&lt;p&gt;Sorry about the delayed response to the previous question also:&lt;/p&gt;

&lt;p&gt;&amp;gt; So is there a guarantee, that in both cases the index is used? &lt;/p&gt;

&lt;p&gt;Exact lookups can use the geo-index in the current implementation only if there are no other criteria (i.e. find(&lt;/p&gt;
{ $within : &amp;lt;blah&amp;gt; }
&lt;p&gt;) and not find(&lt;/p&gt;
{ $within : &amp;lt;blah&amp;gt;, x : 3 }
&lt;p&gt;) ).  If there are additional criteria, the geo-index can&apos;t be used for that query (though you can create an additional regular index to quickly look up exact values).  It&apos;s a little bit awkward, but the geo-indexes store additional details differently (and in a way not really very suitable for further filtering).&lt;/p&gt;

&lt;p&gt;You can always force the geo-index, however, by doing a $within query and specifying very small bounds.&lt;/p&gt;

&lt;p&gt;The test case geoh.js shows how the indices are used with different query types.  &lt;/p&gt;</comment>
                            <comment id="24913" author="greg_10gen" created="Tue, 1 Mar 2011 00:27:52 +0000"  >&lt;p&gt;Indexes used example&lt;/p&gt;</comment>
                            <comment id="24901" author="greg_10gen" created="Mon, 28 Feb 2011 23:55:28 +0000"  >&lt;p&gt;Looked at the code, think it&apos;s working as-designed.  The numbers are a bit hard to interpret, but if you think of everything as divided by a billion, you&apos;re basically saying get everything &amp;gt;201 billion and &amp;lt;201 billion (the second &quot;$lte&quot; just overrides the first).   For individual numbers this will not be true unless the number is actually 201 billion, but for multi-element arrays in mongodb this is interpreted differently, so if an element is &amp;gt; 201 billion and &lt;b&gt;another&lt;/b&gt; element is &amp;lt; 201 billion, it is added.  &lt;/p&gt;

&lt;p&gt;The test case geog.js above is a simplified example, with smaller #s, comparing the $gte/$lte query with and without the geoindexing.&lt;/p&gt;

&lt;p&gt;Also pretty sure geo-queries exactly at the boundaries of regions can be a bit finicky, but that doesn&apos;t seem to affect the script you&apos;ve posted.&lt;/p&gt;
</comment>
                            <comment id="24898" author="greg_10gen" created="Mon, 28 Feb 2011 23:46:27 +0000"  >&lt;p&gt;Example of array gte/lte logic&lt;/p&gt;</comment>
                            <comment id="23423" author="andi" created="Tue, 8 Feb 2011 23:52:13 +0000"  >&lt;p&gt;Additional bug:&lt;/p&gt;

&lt;p&gt;db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500582142917&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(582142917),
		&quot;c&quot; : [
			34378,
			21334
		],
		&quot;t&quot; : [
			4294968392,
			4715874093102
		]
	}
&lt;p&gt;)&lt;br/&gt;
db.bri.insert(&lt;/p&gt;
{
		&quot;_id&quot; : NumberLong(&quot;13500836578420&quot;),
		&quot;p&quot; : &quot;n&quot;,
		&quot;id&quot; : NumberLong(836578420),
		&quot;c&quot; : [
			34378,
			21339
		],
		&quot;t&quot; : [
			315540509818880,
			794568949810,
			2104533975531,
			592705486860,
			803158886206,
			4294967999,
			1327144898739
		]
	}
&lt;p&gt;)&lt;br/&gt;
db&lt;span class=&quot;error&quot;&gt;&amp;#91;&amp;#39;bri&amp;#39;&amp;#93;&lt;/span&gt;.ensureIndex(&lt;/p&gt;
{ c: &apos;2d&apos;, t: 1 }
&lt;p&gt;, &lt;/p&gt;
{ min: 0, max: 66000 }
&lt;p&gt;)&lt;br/&gt;
db.bri.find({c:{$within:{$box:[&lt;span class=&quot;error&quot;&gt;&amp;#91;34373, 21334&amp;#93;&lt;/span&gt;,&lt;span class=&quot;error&quot;&gt;&amp;#91;34378, 21339&amp;#93;&lt;/span&gt;]}}, t:{ &quot;$gte&quot; : 201863462912, &quot;$lte&quot; : 201863462912, &quot;$lte&quot; : 206158430207 }}).limit(200).toArray()&lt;/p&gt;

&lt;p&gt;There should be 0 results, but I get both objects.&lt;/p&gt;</comment>
                            <comment id="23316" author="andi" created="Mon, 7 Feb 2011 23:03:50 +0000"  >&lt;p&gt;The result is correct, but explain() is still irritating me:&lt;/p&gt;

&lt;p&gt;db.br.ensureIndex(&lt;/p&gt;
{ &apos;_i.c&apos;: &apos;2d&apos;, &apos;_i.t&apos;: 1 }
&lt;p&gt;,&lt;/p&gt;
{min:0,max:66000}
&lt;p&gt;)&lt;br/&gt;
db.br.find(&lt;/p&gt;
{&apos;_i.c&apos;:[ 34399, 21331 ],&apos;_i.t&apos;:4294967473}
&lt;p&gt;).explain() &lt;br/&gt;
{&lt;br/&gt;
	&quot;cursor&quot; : &quot;BasicCursor&quot;,&lt;br/&gt;
	&quot;nscanned&quot; : 260296,&lt;br/&gt;
	&quot;nscannedObjects&quot; : 260296,&lt;br/&gt;
	&quot;n&quot; : 1,&lt;br/&gt;
	&quot;millis&quot; : 315,&lt;br/&gt;
	&quot;nYields&quot; : 0,&lt;br/&gt;
	&quot;nChunkSkips&quot; : 0,&lt;br/&gt;
	&quot;isMultiKey&quot; : false,&lt;br/&gt;
	&quot;indexOnly&quot; : false,&lt;br/&gt;
	&quot;indexBounds&quot; : {&lt;/p&gt;

&lt;p&gt;	}&lt;br/&gt;
}&lt;br/&gt;
db.br.find({&apos;_i.c&apos;:{ $within: &lt;/p&gt;
{ $box: [[ 34399, 21331 ], [34400, 21332]] }
&lt;p&gt; },&apos;_i.t&apos;:4294967473}).explain()&lt;br/&gt;
{&lt;br/&gt;
	&quot;cursor&quot; : &quot;GeoBrowse-box&quot;,&lt;br/&gt;
	&quot;nscanned&quot; : 1,&lt;br/&gt;
	&quot;nscannedObjects&quot; : 1,&lt;br/&gt;
	&quot;n&quot; : 1,&lt;br/&gt;
	&quot;millis&quot; : 1,&lt;br/&gt;
	&quot;nYields&quot; : 0,&lt;br/&gt;
	&quot;nChunkSkips&quot; : 0,&lt;br/&gt;
	&quot;isMultiKey&quot; : false,&lt;br/&gt;
	&quot;indexOnly&quot; : false,&lt;br/&gt;
	&quot;indexBounds&quot; : {&lt;/p&gt;

&lt;p&gt;	}&lt;br/&gt;
}&lt;/p&gt;

&lt;p&gt;I usually see &quot;cursor: BasicCursor&quot; in all queries that do &lt;em&gt;not&lt;/em&gt; use an index. I cannot interprete &quot;cursor: GeoBrowse-box&quot;, but one of the developers told me that the reporting for 2d indexes is still not complete.&lt;/p&gt;

&lt;p&gt;So is there a guarantee, that in both cases the index is used?&lt;/p&gt;</comment>
                            <comment id="23052" author="eliot" created="Thu, 3 Feb 2011 16:25:19 +0000"  >&lt;p&gt;Don&apos;t think this was actually fixed, was it?&lt;/p&gt;</comment>
                            <comment id="22812" author="harshw" created="Sat, 29 Jan 2011 23:59:47 +0000"  >&lt;p&gt;Would this fix be back ported to any of the 1.8-rc releases ?&lt;/p&gt;</comment>
                            <comment id="22784" author="greg_10gen" created="Fri, 28 Jan 2011 18:35:53 +0000"  >&lt;p&gt;Fixed by...&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/mongodb/mongo/commit/7fa627b35627e94c94aafe9b0275de665129acd2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/7fa627b35627e94c94aafe9b0275de665129acd2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For $near/$center queries, indexing should work as expected.  Geo-indexing disabled for &lt;del&gt;exact&lt;/del&gt; lookups of positions with additional criteria, as the additional criteria are stored in a diff way from ordinary indices.  &lt;/p&gt;</comment>
                            <comment id="22673" author="greg_10gen" created="Tue, 25 Jan 2011 20:12:42 +0000"  >&lt;p&gt;Second issue as well:&lt;/p&gt;

&lt;p&gt;t = db.geo_circle2;&lt;br/&gt;
t.drop();&lt;br/&gt;
t.ensureIndex(&lt;/p&gt;
{loc : &quot;2d&quot;, categories:1}
&lt;p&gt;, &lt;/p&gt;
{&quot;name&quot;:&quot;placesIdx&quot;, &quot;min&quot;: -100, &quot;max&quot;: 100}
&lt;p&gt;);&lt;br/&gt;
t.insert({ &quot;uid&quot; : 368900 , &quot;loc&quot; : &lt;/p&gt;
{ &quot;x&quot; : -36 , &quot;y&quot; : -8}
&lt;p&gt; ,&quot;categories&quot; : [ &quot;sports&quot; , &quot;hotel&quot; , &quot;restaurant&quot;]});&lt;br/&gt;
t.find({ &quot;loc&quot; : &lt;/p&gt;
{ &quot;x&quot; : -36, &quot;y&quot; : -8}
&lt;p&gt;, &quot;categories&quot; : &quot;sports&quot; })&lt;/p&gt;

&lt;p&gt;Multikeys are stored differently in geoindexes, so normal indexed lookups fail.  Should be addressed at same time.&lt;/p&gt;</comment>
                            <comment id="22632" author="greg_10gen" created="Mon, 24 Jan 2011 22:35:21 +0000"  >&lt;p&gt;Scratch that... looking into a better fix.&lt;/p&gt;</comment>
                            <comment id="22626" author="greg_10gen" created="Mon, 24 Jan 2011 20:11:39 +0000"  >&lt;p&gt;Looked into this... reclassifying as an enhancement.  Explicitly disallowing multikey and geoindexing for now, since with the current matching algorithm used we probably won&apos;t get too much speedup here in any case aside from the lookup from a covered index.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="14276">SERVER-2391</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="10915" name="geog.js" size="625" author="greg_10gen" created="Mon, 28 Feb 2011 23:46:27 +0000"/>
                            <attachment id="10916" name="geoh.js" size="852" author="greg_10gen" created="Tue, 1 Mar 2011 00:27:52 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>16.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 24 Jan 2011 20:11:39 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        12 years, 50 weeks, 2 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ramon.fernandez@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            12 years, 50 weeks, 2 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>andi</customfieldvalue>
            <customfieldvalue>eliot</customfieldvalue>
            <customfieldvalue>greg_10gen</customfieldvalue>
            <customfieldvalue>harshw</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrp89j:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hriclr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>20693</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|ht0fu7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>