<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:24:45 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-2109] Add tests to Index Management spec</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-2109</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;The Index management specification does not include any prose or YAML/JSON tests. We should consider adding some.&lt;/p&gt;

&lt;p&gt;An important part of these tests would be to check that all the options for &lt;tt&gt;createIndexes&lt;/tt&gt; are accepted by the server. As of MongoDB 3.4, the server validates those options (see &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-769&quot; title=&quot;Validate top-level &amp;amp; index spec field names for the createIndexes command&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-769&quot;&gt;&lt;del&gt;SERVER-769&lt;/del&gt;&lt;/a&gt;). This was not the case when the spec was written. &lt;/p&gt;

&lt;p&gt;Testing the options behavior is particularly important because the server&apos;s &lt;tt&gt;createIndexes&lt;/tt&gt; command does not align with many of the option names in the spec.  For example:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;tt&gt;version&lt;/tt&gt; in driver = &lt;tt&gt;v&lt;/tt&gt; on server&lt;/li&gt;
	&lt;li&gt;&lt;tt&gt;defaultLanguage&lt;/tt&gt; in driver = &lt;tt&gt;default_language&lt;/tt&gt; on server&lt;/li&gt;
	&lt;li&gt;&lt;tt&gt;languageOverride&lt;/tt&gt; in driver = &lt;tt&gt;language_override&lt;/tt&gt; on server&lt;/li&gt;
	&lt;li&gt;until &lt;tt&gt;SPEC-1111&lt;/tt&gt;, the spec contained an &lt;tt&gt;expireAfter&lt;/tt&gt; option corresponding to &lt;tt&gt;expireAfterSeconds&lt;/tt&gt; on the server (now renamed to match.)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This is an easy place for errors to be introduced in drivers like Swift that use a BSONEncoder to convert options types to documents, where keys are automatically named by the property names (see SWIFT-404.) &lt;/p&gt;

&lt;p&gt;SPEC-1111 pointed out (and fixed) that &lt;tt&gt;storageEngine&lt;/tt&gt; is supposed to be a document, not a string. A spec test case including the &lt;tt&gt;storageEngine&lt;/tt&gt; option would easily catch this.&lt;/p&gt;</description>
                <environment></environment>
        <key id="743715">DRIVERS-2109</key>
            <summary>Add tests to Index Management spec</summary>
                <type id="14901" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14700&amp;avatarType=issuetype">Spec Change</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="kaitlin.mahar@mongodb.com">Kaitlin Mahar</reporter>
                        <labels>
                    </labels>
                <created>Tue, 23 Apr 2019 16:50:35 +0000</created>
                <updated>Thu, 28 Jul 2022 18:11:24 +0000</updated>
                                                                <component>Index Management</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="2222537" author="kaitlin.mahar" created="Tue, 23 Apr 2019 21:02:47 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jmikola&quot; class=&quot;user-hover&quot; rel=&quot;jmikola&quot;&gt;jmikola&lt;/a&gt; suggested on SPEC-1111 that some of the naming discrepancies are intentionally there so users don&apos;t have to deal with the weird mix of camel case and snake case naming on the server command options (outside the ones I listed above, they are all camel case). I think that is sensible, but the spec should at least note the intentional deviation.&#160;&lt;/p&gt;</comment>
                            <comment id="2222191" author="behackett" created="Tue, 23 Apr 2019 18:00:09 +0000"  >&lt;p&gt;Seems like we need more than just tests. The spec needs to be updated with the proper option names as well.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="11534">SERVER-769</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_10951" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Driver Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10748"><![CDATA[Needed]]></customfieldvalue>

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