<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:58:15 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-2868] Re-enable write concern tests for dropDatabase command</title>
                <link>https://jira.mongodb.org/browse/JAVA-2868</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;Write concern failures for dropDatabase result in failed command in 4.1 server builds, so tests in the driver had to be disabled.&#160; This ticket tracks re-enablement of these tests.&lt;/p&gt;</description>
                <environment></environment>
        <key id="550541">JAVA-2868</key>
            <summary>Re-enable write concern tests for dropDatabase command</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="13201">Fixed</resolution>
                                        <assignee username="jeff.yemin@mongodb.com">Jeffrey Yemin</assignee>
                                    <reporter username="jeff.yemin@mongodb.com">Jeffrey Yemin</reporter>
                        <labels>
                    </labels>
                <created>Tue, 29 May 2018 00:25:02 +0000</created>
                <updated>Sat, 28 Oct 2023 11:22:50 +0000</updated>
                            <resolved>Fri, 16 Nov 2018 13:15:24 +0000</resolved>
                                                    <fixVersion>3.11.0</fixVersion>
                                    <component>Command Operations</component>
                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="2064353" author="xgen-internal-githook" created="Fri, 16 Nov 2018 13:15:15 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Jeff Yemin&apos;, &apos;email&apos;: &apos;jeff.yemin@10gen.com&apos;, &apos;username&apos;: &apos;jyemin&apos;}
&lt;p&gt;Message: Use a failpoint to force write concern errors in drop database tests&lt;/p&gt;

&lt;p&gt;Starting in MongoDB 4.0, the technique of using a write concern with a&lt;br/&gt;
&quot;w&quot; value that is greater than the number of replica set members in&lt;br/&gt;
order to force a write concern fails for the drop database command.&lt;br/&gt;
Also starting in MongoDB 4.0, there is a failpoint available that allows&lt;br/&gt;
tests to force a write concern error.  This patch updates the drop&lt;br/&gt;
database write concern error tests to use the failpoint when the server&lt;br/&gt;
version is &amp;gt;= 4.0&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-2868&quot; title=&quot;Re-enable write concern tests for dropDatabase command&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-2868&quot;&gt;&lt;del&gt;JAVA-2868&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/fbe8ef26efe091a5d607907ed9c16b379c257951&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/fbe8ef26efe091a5d607907ed9c16b379c257951&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1909752" author="xgen-internal-githook" created="Mon, 4 Jun 2018 14:38:05 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;jyemin&apos;, &apos;name&apos;: &apos;Jeff Yemin&apos;, &apos;email&apos;: &apos;jeff.yemin@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-2868&quot; title=&quot;Re-enable write concern tests for dropDatabase command&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-2868&quot;&gt;&lt;del&gt;JAVA-2868&lt;/del&gt;&lt;/a&gt;: Disable drop database write concern tests failing against 4.0 server&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/2470feab5537b1071b422d538747ac7f38d519c9&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/2470feab5537b1071b422d538747ac7f38d519c9&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1902942" author="xgen-internal-githook" created="Tue, 29 May 2018 00:32:23 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;username&apos;: &apos;jyemin&apos;, &apos;name&apos;: &apos;Jeff Yemin&apos;, &apos;email&apos;: &apos;jeff.yemin@10gen.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/JAVA-2868&quot; title=&quot;Re-enable write concern tests for dropDatabase command&quot; class=&quot;issue-link&quot; data-issue-key=&quot;JAVA-2868&quot;&gt;&lt;del&gt;JAVA-2868&lt;/del&gt;&lt;/a&gt;: Disable drop database write concern tests failing against 4.1 server&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-java-driver/commit/d0a4c7d29b8636e2559afd987ec88edc843aeaee&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-java-driver/commit/d0a4c7d29b8636e2559afd987ec88edc843aeaee&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="550540">SERVER-35265</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|htq5mf:</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>