<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 22:02:29 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-1391] reset client options when returned to the pool</title>
                <link>https://jira.mongodb.org/browse/CXX-1391</link>
                <project id="11980" key="CXX">C++ Driver</project>
                    <description>&lt;p&gt;When I acquire a client from a pool and manually modify the write concern at client level (client::write_concern(wc)), the modified client is released to the pool.&lt;/p&gt;

&lt;p&gt;Later on, if I acquire a new client from this pool, I may end-up  with a client with the modified write concern, which does not correspond to the one the pool has been created with.&lt;/p&gt;

&lt;p&gt;With current behavior, application code seems to be responsible to reset the client write concern to an appropriate value before it is released to the pool. &lt;/p&gt;

&lt;p&gt;The pool should take care of resetting the write concern to an appropriate value or the write_concern of a client acquired from the pool should be read-only.&lt;/p&gt;</description>
                <environment></environment>
        <key id="403110">CXX-1391</key>
            <summary>reset client options when returned to the pool</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</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="Pierre">Pierre Petitprez</reporter>
                        <labels>
                    </labels>
                <created>Wed, 12 Jul 2017 16:08:20 +0000</created>
                <updated>Wed, 12 Jul 2017 21:37:08 +0000</updated>
                            <resolved>Wed, 12 Jul 2017 21:36:39 +0000</resolved>
                                    <version>3.1.1</version>
                                                    <component>Implementation</component>
                                        <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="1620522" author="david.golden" created="Wed, 12 Jul 2017 21:36:39 +0000"  >&lt;p&gt;Hi. Thanks for the bug report and are sorry that you experienced this problem.  Unfortunately, this is a limitation of libmongoc.  In the next release of the C++ driver (3.2.0), modifying client options will be deprecated (see &lt;a href=&quot;https://jira.mongodb.org/browse/CXX-1086&quot; title=&quot;Deprecate non-const methods on mongocxx::client&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CXX-1086&quot;&gt;&lt;del&gt;CXX-1086&lt;/del&gt;&lt;/a&gt;).  A future version of libmongoc will remove the ability to modify options at all (&lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-938&quot; title=&quot;Prohibit setting options on pooled clients&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-938&quot;&gt;CDRIVER-938&lt;/a&gt;) at which point the C++ driver will have to do the same.&lt;/p&gt;

&lt;p&gt;We recommend setting default client options in the URI string used to configure the pool or setting operation-specific options such as write concern on the database/collection objects acquired from a checked out client.  This will avoid the problem you experienced.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="323057">CXX-1086</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="234385">CDRIVER-938</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|ht2nbz:</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>