<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:59: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-3557] Test 3.6 drivers against 4.2 servers</title>
                <link>https://jira.mongodb.org/browse/JAVA-3557</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;See &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-788&quot; title=&quot;Test 3.6 drivers against 4.2 servers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-788&quot;&gt;&lt;del&gt;DRIVERS-788&lt;/del&gt;&lt;/a&gt; for details.&lt;/p&gt;</description>
                <environment></environment>
        <key id="1058303">JAVA-3557</key>
            <summary>Test 3.6 drivers against 4.2 servers</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="jeff.yemin@mongodb.com">Jeffrey Yemin</assignee>
                                    <reporter username="dbeng-pm-bot">PM Bot</reporter>
                        <labels>
                    </labels>
                <created>Tue, 17 Dec 2019 19:39:11 +0000</created>
                <updated>Wed, 15 Jan 2020 01:27:23 +0000</updated>
                            <resolved>Sat, 11 Jan 2020 21:58:11 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="2725731" author="behackett" created="Wed, 15 Jan 2020 01:27:23 +0000"  >&lt;p&gt;Great. Thanks.&lt;/p&gt;</comment>
                            <comment id="2725718" author="jeff.yemin" created="Wed, 15 Jan 2020 01:05:24 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=behackett&quot; class=&quot;user-hover&quot; rel=&quot;behackett&quot;&gt;behackett&lt;/a&gt;, no.&#160; Except for undigested passwords, all the breaking server changes require the user to opt in to the feature that was removed in the server.&#160; For &lt;tt&gt;autoIndexId&lt;/tt&gt;, as an example, the driver&apos;s default is to not include the field in the &lt;tt&gt;createCollection&lt;/tt&gt; command.&#160; Only if the application opts in by specifying &lt;tt&gt;autoIndexId&lt;/tt&gt; of &lt;tt&gt;false&lt;/tt&gt; will the application stop working.&#160;&#160;&lt;/p&gt;

&lt;p&gt;Good point about undigested password changes being a 4.0 issue.&#160; I hadn&apos;t saved my work from the ticket verifying 4.0 support, so I just fixed everything all over again.&lt;/p&gt;</comment>
                            <comment id="2725664" author="behackett" created="Wed, 15 Jan 2020 00:35:56 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jeff.yemin&quot; class=&quot;user-hover&quot; rel=&quot;jeff.yemin&quot;&gt;jeff.yemin&lt;/a&gt;, other than the changes that are well documented in the server 4.2 release notes, and the undigested passwords change that came along with MongoDB 4.0, did any of these server changes require changes in the 4.2 support release of the Java driver to keep applications from breaking? The autoIndexId change perhaps?&lt;/p&gt;</comment>
                            <comment id="2720379" author="jeff.yemin" created="Sat, 11 Jan 2020 21:57:07 +0000"  >&lt;p&gt;Branch with all tests passing:&#160;&lt;a href=&quot;https://github.com/jyemin/mongo-java-driver/tree/3.6.x-test-against-4.0-and-4.2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/jyemin/mongo-java-driver/tree/3.6.x-test-against-4.0-and-4.2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Evergreen patch:&#160;&#160;&lt;a href=&quot;https://evergreen.mongodb.com/version/5e1a3f31e3c33105154a0747&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/version/5e1a3f31e3c33105154a0747&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Summary of changes made on the branch:&lt;br/&gt;
&#160;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;make undigested passwords the default for user management commands (requires updated driver)&lt;/li&gt;
	&lt;li&gt;writeErrors have more info so assertion has to be modified (just a test change)&lt;/li&gt;
	&lt;li&gt;group command is no longer supported, so skipping those tests&lt;/li&gt;
	&lt;li&gt;parallelScan command is no longer supported, so skipping those tests&lt;/li&gt;
	&lt;li&gt;snapshot option for find command no longer supported, so skipping those tests&lt;/li&gt;
	&lt;li&gt;min, max, and maxScan behavior modified (requires index), so skipping those tests&lt;/li&gt;
	&lt;li&gt;eval command no longer supported, so skipping those tests&lt;/li&gt;
	&lt;li&gt;hint field on aggregate test failing, so skipping those tests&lt;/li&gt;
	&lt;li&gt;autoIndexId option on createCollection command no longer supported, so skipping those tests&lt;/li&gt;
	&lt;li&gt;mmap storage engine no longer supported, so skipping those tests that specify it&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Conclusions:&lt;/p&gt;

&lt;p&gt;Testing did not find anything in the Java driver itself that will effect migrations from MongoDB 3.6 t MongoDB 4.2.  So long as applications are not using any MongoDB features that are no longer supported in 4.2, they should be fine.  The only backwards-breaking changes in the server that required a corresponding change in the driver was in the area of user management commands, but since Atlas does not allow user management to be performed from applications, it should not affect applications that are being migrated to Atlas.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="1058289">DRIVERS-788</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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|hvydzr:</customfieldvalue>

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