<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:57:57 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>[JAVA-2739] Getter for Namespace in Aggregation Operation</title>
                <link>https://jira.mongodb.org/browse/JAVA-2739</link>
                <project id="10006" key="JAVA">Java Driver</project>
                    <description>&lt;p&gt;The class com.mongodb.operation.FindOperation does provide already a getter for the &quot;namespace&quot; field. Can you please also provide the getter in com.mongodb.operation.AggregateOperation? &lt;/p&gt;


</description>
                <environment></environment>
        <key id="485408">JAVA-2739</key>
            <summary>Getter for Namespace in Aggregation Operation</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="5" iconUrl="https://jira.mongodb.org/images/icons/priorities/trivial.svg">Trivial - P5</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="-1">Unassigned</assignee>
                                    <reporter username="fmisir">Fethullah</reporter>
                        <labels>
                    </labels>
                <created>Sun, 21 Jan 2018 19:06:59 +0000</created>
                <updated>Thu, 11 Oct 2018 20:28:05 +0000</updated>
                            <resolved>Thu, 11 Oct 2018 20:28:05 +0000</resolved>
                                                                    <component>API</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="2030633" author="jeff.yemin" created="Thu, 11 Oct 2018 20:28:05 +0000"  >&lt;p&gt;We plan to deprecate the operation classes in the next release and then move them to an internal package.  As such, we won&apos;t be enhancing any operation classes for public use.&lt;/p&gt;</comment>
                            <comment id="1781301" author="fmisir" created="Mon, 22 Jan 2018 20:49:46 +0000"  >&lt;p&gt;Hi Ross,&lt;/p&gt;

&lt;p&gt;for me it is pretty difficult to write good tests for components which are retrieving data from MongoDB.&lt;br/&gt;
The available inmemory databases do not completely support aggregate queries which i&apos;am using extensivly in my personal project.&lt;/p&gt;

&lt;p&gt;Therefor i developed a small library. The library  delegates MongoDB queries to a HTTP Server (WireMock) using a custom AsyncOperationExecutor. The response will be parsed to Document(s) and passed to SingleResultCallback of the executor.&lt;br/&gt;
This approach allows me to write tests for my MongoDB components, as simple as writing tests for external HTTP API&apos;s. &lt;/p&gt;

&lt;p&gt;To improve the stub matching, i need the collectionName from the namespace of AggregateOperation. &lt;br/&gt;
I implemented already a workaround using reflection. But it would be getter so that it is consistent with FindOperation.&lt;/p&gt;

&lt;p&gt;Fethullah &lt;/p&gt;</comment>
                            <comment id="1780399" author="ross@10gen.com" created="Mon, 22 Jan 2018 09:16:46 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=fmisir&quot; class=&quot;user-hover&quot; rel=&quot;fmisir&quot;&gt;fmisir&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;I&apos;m interested to hear that you are using the Operations classes directly.  Can you explain more about your usecase? And any reasoning for using them over the higher API&apos;s? eg: the Mongo Java Driver / Async Driver&lt;/p&gt;

&lt;p&gt;Ross&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <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|htfwdj:</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>