<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:52:53 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>[JAVA-704] Java Driver caches indexes internally, which causes indexes if indexes are managed by multiple apps</title>
                <link>https://jira.mongodb.org/browse/JAVA-704</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;Java Driver caches index information when using DBCollection.ensureIndex method that makes it unusable if there are multiple apps managing indexing/db.&lt;/p&gt;

&lt;p&gt;DBCollection.createIndex on the other hand does not cache this information.&lt;/p&gt;

&lt;p&gt;The mongo console does not have the createIndex method, but instead it has ensureIndex.&lt;/p&gt;

&lt;p&gt;The behavior of the JS vs Java ensureIndex is expected to be the same.&lt;/p&gt;

&lt;p&gt;The caching behavior is not documented anywhere.&lt;/p&gt;

&lt;p&gt;In addition, adding this kind of functionality to a db driver does not make sense, as it should serve as a proxy between the applications and the database. The application can decide whether or not to cache such information. &lt;/p&gt;</description>
                <environment>Java Driver 2.8.0</environment>
        <key id="57912">JAVA-704</key>
            <summary>Java Driver caches indexes internally, which causes indexes if indexes are managed by multiple apps</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</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="3">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="okrook">Oleg Krook</reporter>
                        <labels>
                    </labels>
                <created>Thu, 29 Nov 2012 17:19:07 +0000</created>
                <updated>Fri, 30 Nov 2012 16:32:25 +0000</updated>
                            <resolved>Fri, 30 Nov 2012 02:29:42 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="203269" author="okrook" created="Fri, 30 Nov 2012 16:32:25 +0000"  >&lt;p&gt;Thanks, it makes sense.&lt;/p&gt;</comment>
                            <comment id="203254" author="jeff.yemin" created="Fri, 30 Nov 2012 16:23:25 +0000"  >&lt;p&gt;The reason I marked this as a duplicate is that I think all caching behavior for indices should be removed from the driver.&lt;/p&gt;</comment>
                            <comment id="203165" author="okrook" created="Fri, 30 Nov 2012 14:37:59 +0000"  >&lt;p&gt;I do not think the defects are related. The ensureIndex is advocated to be used on the www.mongodb.com, however the caching behavior of it is not documented anywhere. I would consider this to be a documentation defect after I&apos;ve learned the createIndex should have been used instead.&lt;/p&gt;</comment>
                            <comment id="202778" author="jeff.yemin" created="Fri, 30 Nov 2012 02:29:35 +0000"  >&lt;p&gt;This issue duplicates &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-667&quot; title=&quot;Caching Behavior Inconsistent when Dropping Indexes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-667&quot;&gt;&lt;del&gt;JAVA-667&lt;/del&gt;&lt;/a&gt;, so I&apos;m going to close it.&lt;/p&gt;</comment>
                            <comment id="202359" author="ian@10gen.com" created="Thu, 29 Nov 2012 17:26:06 +0000"  >&lt;p&gt;from Steps To Reproduce:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;1. App1 uses DBColletion.ensureIndex to create and index &lt;br/&gt;
2. App2 drops the database &lt;br/&gt;
3. App1 validates that the db is dropped and calls DBColletion.ensureIndex again to ensure indexes.&lt;/p&gt;&lt;/blockquote&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="53182">JAVA-667</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrku9j:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>35365</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>