<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:21:12 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-298] Update Command Spec to include setVersion, electionId and lastOp</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-298</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;Returning the current setVersion, electionId and lastOp would allow drivers to avoid pinging the server using ismaster continuously to establish the topology of the replicaset as well as provide monotonic read operations.&lt;br/&gt;
In case of a primary election a new electionId would be returned and in the case of a new secondary being added or removed a new setVersion would be returned.&lt;br/&gt;
If adding a new secondary that caused an election the server might return both a new setVersion and a new electionId.&lt;br/&gt;
the lastOp field would allow for simpler monotonic read operations&lt;/p&gt;</description>
                <environment></environment>
        <key id="277966">DRIVERS-298</key>
            <summary>Update Command Spec to include setVersion, electionId and lastOp</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</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="david.golden@mongodb.com">David Golden</assignee>
                                    <reporter username="rathi.gnanasekaran">Rathi Gnanasekaran</reporter>
                        <labels>
                    </labels>
                <created>Wed, 6 Apr 2016 18:20:01 +0000</created>
                <updated>Tue, 4 Oct 2016 20:33:48 +0000</updated>
                            <resolved>Tue, 4 Oct 2016 20:33:48 +0000</resolved>
                                                                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="1400137" author="david.golden" created="Tue, 4 Oct 2016 20:33:48 +0000"  >&lt;p&gt;With updates to SDAM and the implementation of Max Staleness, the need for this is largely addressed.&lt;/p&gt;</comment>
                            <comment id="1306534" author="behackett" created="Sat, 25 Jun 2016 00:45:00 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=david.golden&quot; class=&quot;user-hover&quot; rel=&quot;david.golden&quot;&gt;david.golden&lt;/a&gt;, is this ticket still relevant? For maxStalenessMS we decided not to use information returned by write commands.&lt;/p&gt;</comment>
                            <comment id="1228017" author="behackett" created="Wed, 6 Apr 2016 18:32:15 +0000"  >&lt;p&gt;Is the idea here to re-evaluate the topology after every command (literally every operation with MongoDB 3.2+)? &lt;/p&gt;</comment>
                            <comment id="1227998" author="behackett" created="Wed, 6 Apr 2016 18:23:47 +0000"  >&lt;p&gt;I don&apos;t think we can stop pinging the server with ismaster until we drop support for all server versions that don&apos;t already return this information.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="136099">SERVER-13909</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|hsk64n:</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>