<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:23:06 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>[DRIVERS-1253] Make dropIndexes abort in-progress index builds</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-1253</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>
    &lt;div class=&quot;panel&quot; style=&quot;background-color: #c2d2c2;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelHeader&quot; style=&quot;border-bottom-width: 1px;background-color: #239eb0;&quot;&gt;&lt;b&gt;Downstream Change Summary&lt;/b&gt;&lt;/div&gt;&lt;div class=&quot;panelContent&quot; style=&quot;background-color: #c2d2c2;&quot;&gt;
&lt;p&gt;    The &quot;dropIndexes&quot; command can now be used to abort in-progress index builds being built in the background. As we can only abort at the builder level granularity, the user must specify all the indexes being built by a single index builder to abort it successfully.&lt;/p&gt;

&lt;p&gt;This command still retains the previous behaviour of returning &quot;BackgroundOperationInProgressForNamespace&quot; when trying to drop a ready index while there are index builds still in-progress.&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h2&gt;&lt;a name=&quot;DescriptionofLinkedTicket&quot;&gt;&lt;/a&gt;Description of Linked Ticket&lt;/h2&gt;
&lt;p&gt;    dropIndexes should abort in-progress index builds. This should be done after &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-37763&quot; title=&quot;Make it possible to abort index builds&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-37763&quot;&gt;&lt;del&gt;SERVER-37763&lt;/del&gt;&lt;/a&gt; makes it possible to abort an index build.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-37727&quot; title=&quot;Enhance dropIndexes to accept multiple specific indexes to drop&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-37727&quot;&gt;&lt;del&gt;SERVER-37727&lt;/del&gt;&lt;/a&gt; will enhance dropIndexes to receive an array of indexes as arguments. This task will only abort in-progress index builds if the user specifies all of the indexes that a single builder is building together. A createIndexes command can start multiple indexes building together on one builder and we currently only have the granularity to abort all or none of the indexes on a builder.&lt;/p&gt;

&lt;p&gt;Lastly, dropIndexes will not write a dropIndexes oplog entry if aborting in-progress builds. Aborting the index will produce an abortIndexBuilds oplog entry, which suffices. This allows rollback via refetch to know that an index was fully built prior to a dropIndexes oplog entry.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="1156726">DRIVERS-1253</key>
            <summary>Make dropIndexes abort in-progress index builds</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="backlog-server-pm">Backlog - Core Eng Program Management Team</reporter>
                        <labels>
                    </labels>
                <created>Tue, 18 Feb 2020 06:07:41 +0000</created>
                <updated>Fri, 27 May 2022 01:28:02 +0000</updated>
                            <resolved>Tue, 26 May 2020 18:30:16 +0000</resolved>
                                                                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="3092889" author="jmikola@gmail.com" created="Mon, 18 May 2020 16:29:32 +0000"  >&lt;p&gt;During triage, let&apos;s determine if this should be closed and consolidated in favor of &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-745&quot; title=&quot;Specify how drivers handle &amp;quot;ns not found&amp;quot; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-745&quot;&gt;&lt;del&gt;DRIVERS-745&lt;/del&gt;&lt;/a&gt;, given that both of these issues depend on &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-41365&quot; title=&quot;Improve unhelpful error &amp;quot;ns not found&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-41365&quot;&gt;&lt;del&gt;SERVER-41365&lt;/del&gt;&lt;/a&gt; and takeaway from recent discussions between leads and server was that drivers should (a) start relying on the error code if they&apos;re not already and (b) augment the server&apos;s error message since the server cannot do so without breaking BC with older driver versions.&lt;/p&gt;</comment>
                            <comment id="3075921" author="jmikola@gmail.com" created="Fri, 8 May 2020 15:07:48 +0000"  >&lt;p&gt;I think this should be re-opened for triaging based on later comments in &lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-745&quot; title=&quot;Specify how drivers handle &amp;quot;ns not found&amp;quot; errors&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-745&quot;&gt;&lt;del&gt;DRIVERS-745&lt;/del&gt;&lt;/a&gt;. It looks like we missed a breaking change due to a change in the error message when a collection does not exist.&lt;/p&gt;</comment>
                            <comment id="2905511" author="esha.bhargava" created="Mon, 24 Feb 2020 18:59:32 +0000"  >&lt;p&gt;No Drivers changes needed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                            <outwardlinks description="depends on">
                                        <issuelink>
            <issuekey id="623458">SERVER-37726</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="779036">SERVER-41365</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="962828">DRIVERS-745</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|hwff27:</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>
                                                                                                                                                                                                                                        <customfield id="customfield_22279" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Server Compat</customfieldname>
                        <customfieldvalues>
                                        <label>4.3</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    </customfields>
    </item>
</channel>
</rss>