<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:24:40 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-2081] Clarify usage of aggregation pipeline in CRUD spec</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-2081</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;As noted by &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=jmikola&quot; class=&quot;user-hover&quot; rel=&quot;jmikola&quot;&gt;jmikola&lt;/a&gt; in &lt;a href=&quot;https://github.com/mongodb/mongo-php-library/pull/670#discussion_r317378293&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-php-library/pull/670#discussion_r317378293&lt;/a&gt;, the CRUD spec does not specify any expected driver behaviour when a user passes an aggregation pipeline as &lt;tt&gt;update&lt;/tt&gt; option to a &lt;tt&gt;replace&lt;/tt&gt; operation. The spec should clarify this and also add spec tests covering the expected behaviour.&lt;/p&gt;</description>
                <environment></environment>
        <key id="905952">DRIVERS-2081</key>
            <summary>Clarify usage of aggregation pipeline in CRUD spec</summary>
                <type id="14901" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14700&amp;avatarType=issuetype">Spec Change</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="andreas.braun@mongodb.com">Andreas Braun</reporter>
                        <labels>
                    </labels>
                <created>Mon, 26 Aug 2019 10:06:03 +0000</created>
                <updated>Thu, 31 Mar 2022 14:21:01 +0000</updated>
                                                                <component>CRUD</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="2387780" author="jmikola@gmail.com" created="Tue, 27 Aug 2019 04:53:25 +0000"  >&lt;p&gt;Furthermore, drivers such as C and PHP reject empty arrays for update pipelines. Per my analysis in &lt;a href=&quot;https://github.com/mongodb/mongo-php-library/pull/670#discussion_r317378507&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-php-library/pull/670#discussion_r317378507&lt;/a&gt;, the server actually accepts this and interprets it as a NOP. I don&apos;t think there is a problem with drivers rejecting such values, but we&apos;d do well to codify this in the spec one way or the other.&lt;/p&gt;

&lt;p&gt;FWIW, I believe all drivers allow empty pipelines for &lt;tt&gt;aggregate&lt;/tt&gt;, but that&apos;s not directly comparable as an empty pipeline there is effectively an unfiltered find query. In that sense, &lt;tt&gt;aggregate&lt;/tt&gt; still does &lt;em&gt;something&lt;/em&gt;, as opposed to a NOP-ing &lt;tt&gt;update&lt;/tt&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                                        </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_10951" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Driver Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10748"><![CDATA[Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrer7b:</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>