<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:13:35 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>[CDRIVER-1911] Query and command cursor inconsistencies</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-1911</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;[reposted from my email as requested]&lt;/p&gt;

&lt;p&gt;In trying to fix &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-1001&quot; title=&quot;mongocxx::cursor.begin() increments the iterator&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-1001&quot;&gt;&lt;del&gt;CXX-1001&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-1100&quot; title=&quot;Having more than one iterator per cursor violates mongoc lifecycle constraints&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-1100&quot;&gt;&lt;del&gt;CXX-1100&lt;/del&gt;&lt;/a&gt;, I kept getting test failures implementing with the libmongoc cursor sent/is_alive functions.  I wound up implementing what I needed on the mongocxx side to track &quot;sent&quot; and &quot;alive&quot; there and got it working.&lt;/p&gt;

&lt;p&gt;The difference appears with command cursors.  I don&apos;t have time to give an SSCCE (sorry) or narrow it down and our own tests are too sparse to be sure of that diagnosis, but it might be something to look into and I didn&apos;t want it lost.&lt;/p&gt;

&lt;p&gt;(I.e. construct a cursor from a query and from something like list collections, then see if you get the same answers from sent/is_alive/current.)&lt;/p&gt;</description>
                <environment></environment>
        <key id="330770">CDRIVER-1911</key>
            <summary>Query and command cursor inconsistencies</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</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="jesse@mongodb.com">A. Jesse Jiryu Davis</assignee>
                                    <reporter username="david.golden@mongodb.com">David Golden</reporter>
                        <labels>
                    </labels>
                <created>Wed, 9 Nov 2016 16:50:16 +0000</created>
                <updated>Sat, 12 Nov 2016 02:05:03 +0000</updated>
                            <resolved>Sat, 12 Nov 2016 01:45:09 +0000</resolved>
                                    <version>1.5.0</version>
                                    <fixVersion>1.5.0</fixVersion>
                                                        <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="1432556" author="jesse" created="Sat, 12 Nov 2016 01:45:09 +0000"  >&lt;p&gt;Discussion with David and Rassi: we think the inconsistency they saw is that a listCollections command cursor is &quot;sent&quot; as soon as it&apos;s created, whereas a legacy system.namespaces cursor isn&apos;t &quot;sent&quot; until the first mongoc_cursor_next call. Same for listDatabases, maybe other APIs.&lt;/p&gt;

&lt;p&gt;What the C++ driver really needs is a way to know if the cursor has been &lt;b&gt;used&lt;/b&gt; at all, not whether it&apos;s been &quot;sent&quot;, from the C Driver&apos;s perspective. The C++ driver now manages this state itself and we&apos;re going to remove mongoc_cursor_sent before releasing 1.5.0.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="326924">CDRIVER-1886</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|hsrq1j:</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>