<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:02:21 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>[CXX-1351] Investigate implementing the index view API described in the index management spec</title>
                <link>https://jira.mongodb.org/browse/CXX-1351</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;The index management spec details two APIs, the &quot;standard API&quot; and the &quot;index view API&quot; and gives drivers the option of implementing either. mongocxx currently implements all of the standard API except the `create_indexes`, `drop_index`, and `drop_indexes` methods. We should decide whether we want to implement the index view spec and deprecate the collection methods pertaining to indexes or simply finish implementing the standard API.&lt;/p&gt;</description>
                <environment></environment>
        <key id="388539">CXX-1351</key>
            <summary>Investigate implementing the index view API described in the index management spec</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="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="sam.rossi@mongodb.com">Samuel Rossi</reporter>
                        <labels>
                    </labels>
                <created>Tue, 30 May 2017 21:11:26 +0000</created>
                <updated>Thu, 31 Mar 2022 14:18:21 +0000</updated>
                                                                            <component>API</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="1583299" author="david.golden" created="Tue, 30 May 2017 21:38:12 +0000"  >&lt;p&gt;I agree that we should finish the &quot;standard API&quot;.&lt;/p&gt;

&lt;p&gt;I wonder if it might make sense to implement an indexModel that takes a BSON document for options so that we&apos;re forward compatible instead of changing the index::options class every time the server adds an indexing feature.  Or PIMPL index::options as another way of doing a similar thing.&lt;/p&gt;</comment>
                            <comment id="1583286" author="sam.rossi" created="Tue, 30 May 2017 21:28:46 +0000"  >&lt;p&gt;Given that we already have `create_index` and `list_indexes` as methods on collection and that the spec gives no preference to either of the API choices, I think that it would be better for us to implement the remainder of the standard API rather than to switch to the index view API. Having the aforementioned methods present in addition to the index view API seems like it could confuse users (who might wonder why we have collection::create_index but not collection::drop_index), and I don&apos;t think that switching to the index view API is a big enough win to be worth deleting the methods and breaking compatibility. One alternative might be to fully implement both APIs, but I don&apos;t think that duplicating the functionality across two APIs is as clean as just using the standard API, which users of the driver will already be partially familiar with and using.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="366253">CXX-1272</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|hxk87b:</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>