<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:06:33 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-2638] ConnectionId returned in heartbeats may be int64</title>
                <link>https://jira.mongodb.org/browse/CXX-2638</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;This ticket was split from &lt;tt&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2503&quot; title=&quot;ConnectionId returned in heartbeats may be int64&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2503&quot;&gt;DRIVERS-2503&lt;/a&gt;&lt;/tt&gt;, please see that ticket for a detailed description. &lt;/p&gt;</description>
                <environment></environment>
        <key id="2236177">CXX-2638</key>
            <summary>ConnectionId returned in heartbeats may be int64</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="10300" iconUrl="https://jira.mongodb.org/images/icons/priorities/medium.svg">Unknown</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="13202">Works as Designed</resolution>
                                        <assignee username="kevin.albertson@mongodb.com">Kevin Albertson</assignee>
                                    <reporter username="dbeng-pm-bot">PM Bot</reporter>
                        <labels>
                    </labels>
                <created>Wed, 18 Jan 2023 15:45:57 +0000</created>
                <updated>Fri, 27 Oct 2023 13:13:30 +0000</updated>
                            <resolved>Wed, 26 Apr 2023 13:41:46 +0000</resolved>
                                                                                        <votes>1</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="5377399" author="kevin.albertson" created="Wed, 26 Apr 2023 13:41:46 +0000"  >&lt;p&gt;Bug is fixed in the C driver.&lt;/p&gt;

&lt;p&gt;The only relevant change to the C++ driver is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;NOTE: If the client and server connectionId fields are part of the driver&apos;s public API, you may have to add new int64 connectionId fields and deprecate the existing int32 fields.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;The C++ driver does not have public API for the server connectionId. Noted in &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-2311&quot; title=&quot;Add server connectionId to command monitoring events&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-2311&quot;&gt;CXX-2311&lt;/a&gt; that when public API for the server connectionId is added, it must be an int64.&lt;/p&gt;</comment>
                            <comment id="5377391" author="kevin.albertson" created="Wed, 26 Apr 2023 13:39:45 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=vgrippa%40gmail.com&quot; class=&quot;user-hover&quot; rel=&quot;vgrippa@gmail.com&quot;&gt;vgrippa@gmail.com&lt;/a&gt; the connectionId parsing is handled by the C driver. The bug is fixed in &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-4502&quot; title=&quot;libmongoc expects connectionId in hello response to be int32&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-4502&quot;&gt;&lt;del&gt;CDRIVER-4502&lt;/del&gt;&lt;/a&gt; (to handle int32) and &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-4593&quot; title=&quot;C Driver fails to validate double type connectionId during handshake process&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-4593&quot;&gt;&lt;del&gt;CDRIVER-4593&lt;/del&gt;&lt;/a&gt; (to handle double). Upgrading the C driver to 1.23.3 is expected to resolve this issue for the C++ driver.&lt;/p&gt;</comment>
                            <comment id="5286592" author="vgrippa@gmail.com" created="Mon, 20 Mar 2023 22:17:11 +0000"  >&lt;p&gt;Do we have more information on this? Why the issue raises only 3.7.0, but it works with 3.6.0?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10423">
                    <name>Gantt End to End</name>
                                            <outwardlinks description="has to be finished together with">
                                        <issuelink>
            <issuekey id="1821041">CXX-2311</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10620">
                    <name>Issue split</name>
                                                                <inwardlinks description="split from">
                                        <issuelink>
            <issuekey id="2188290">DRIVERS-2503</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="2236176">CDRIVER-4557</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|i19nc0:</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_21457" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Upstream Changes Summary</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/browse/DRIVERS-2503&quot; title=&quot;ConnectionId returned in heartbeats may be int64&quot; class=&quot;issue-link&quot; data-issue-key=&quot;DRIVERS-2503&quot;&gt;DRIVERS-2503&lt;/a&gt;:&lt;br/&gt;
The &lt;tt&gt;connectionId&lt;/tt&gt; in the &lt;tt&gt;hello&lt;/tt&gt; (or legacy hello) response can be an &lt;tt&gt;int32&lt;/tt&gt;, &lt;tt&gt;double&lt;/tt&gt;, or &lt;tt&gt;int64&lt;/tt&gt;. Many drivers assume an &lt;tt&gt;int32&lt;/tt&gt;, which may result in &lt;tt&gt;connectionId&lt;/tt&gt; truncation or connection failure. Drivers should ensure that the server&apos;s &lt;tt&gt;connectionId&lt;/tt&gt; (and the client &lt;tt&gt;connectionId&lt;/tt&gt; for consistency) is expressed as a numeric type capable of holding an &lt;tt&gt;int64&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;NOTE: If the client and server &lt;tt&gt;connectionId&lt;/tt&gt; fields are part of the driver&apos;s public API, you may have to add new &lt;tt&gt;int64&lt;/tt&gt; &lt;tt&gt;connectionId&lt;/tt&gt; fields and deprecate the existing &lt;tt&gt;int32&lt;/tt&gt; fields. On the next major version bump, the deprecated &lt;tt&gt;int32&lt;/tt&gt; fields should be removed.&lt;/p&gt;</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>