<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:44:31 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>[SERVER-36941] Option to provide &quot;before image&quot; with change streams</title>
                <link>https://jira.mongodb.org/browse/SERVER-36941</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;It would be useful to be able to see the data as it was before the change made to it when monitoring via change streams.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="597747">SERVER-36941</key>
            <summary>Option to provide &quot;before image&quot; with change streams</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="13201">Fixed</resolution>
                                        <assignee username="bernard.gorman@mongodb.com">Bernard Gorman</assignee>
                                    <reporter username="arnie.listhaus@mongodb.com">Arnie Listhaus</reporter>
                        <labels>
                            <label>change-streams-improvements</label>
                    </labels>
                <created>Thu, 30 Aug 2018 15:24:09 +0000</created>
                <updated>Sun, 29 Oct 2023 22:28:32 +0000</updated>
                            <resolved>Tue, 29 Mar 2022 16:23:38 +0000</resolved>
                                                    <fixVersion>6.0.0-rc0</fixVersion>
                                    <component>Querying</component>
                                        <votes>38</votes>
                                    <watches>74</watches>
                                                                                                                <comments>
                            <comment id="4872817" author="schwerin" created="Mon, 3 Oct 2022 14:27:40 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ywu%40stripe.com&quot; class=&quot;user-hover&quot; rel=&quot;ywu@stripe.com&quot;&gt;ywu@stripe.com&lt;/a&gt;, I&apos;m afraid that documenting that behavior prior to 6.0 is a mistake on our part. We had a prototype implementation on earlier releases that we used for some targeted use cases at MongoDB, but we did not feel that implementation was appropriate for general release. It relied on putting document pre-images into the oplog, which negatively impacted the amount of oplog (and change events) that could be retained, especially for users with large document sizes. The implementation in 6.0 and later relies on the primary and secondaries storing pre-image documents as necessary when they apply updates, instead. This reduces pressure on the oplog considerably, which in a quirk of the MongoDB implementation, also substantially reduces pressure on the write-ahead log, reducing the I/O burden of the feature.&lt;/p&gt;

&lt;p&gt;It is possible to activate the pre-6.0 feature (it requires changing the configuration files on the replica nodes), but it is not supported and we would not be able to support any problems you encountered with it.&lt;/p&gt;</comment>
                            <comment id="4871641" author="JIRAUSER1269225" created="Mon, 3 Oct 2022 03:51:14 +0000"  >&lt;p&gt;Thanks for the clarification, it&apos;s helpful - I see there is `fullDocumentBeforeChange` option in 4.4&apos;s changeStream operator &lt;a href=&quot;https://www.mongodb.com/docs/v4.4/reference/operator/aggregation/changeStream/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.mongodb.com/docs/v4.4/reference/operator/aggregation/changeStream/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Looking at the code, it&apos;s doing a lookup in oplog with UUID, which seems to be doing the right thing &#8211; is there any known correctness and performance issue if we use it to get pre-image?&#160;&lt;/p&gt;</comment>
                            <comment id="4870657" author="schwerin" created="Sat, 1 Oct 2022 12:02:55 +0000"  >&lt;p&gt;Please check out the &lt;a href=&quot;https://www.mongodb.com/docs/manual/changeStreams/#change-streams-with-document-pre--and-post-images&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;documentation&lt;/a&gt; for instructions about getting precise pre- and post-images. The code you have linked in your comment, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ywu%40stripe.com&quot; class=&quot;user-hover&quot; rel=&quot;ywu@stripe.com&quot;&gt;ywu@stripe.com&lt;/a&gt;, is the code for the non-precise behavior which is still available.&lt;/p&gt;</comment>
                            <comment id="4870601" author="JIRAUSER1269225" created="Sat, 1 Oct 2022 09:05:18 +0000"  >&lt;p&gt;Hi it looks like there is still a race condition when we do the post-image look up &lt;a href=&quot;https://github.com/mongodb/mongo/blob/master/src/mongo/db/pipeline/document_source_change_stream_add_post_image.cpp#L203-L205&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/blob/master/src/mongo/db/pipeline/document_source_change_stream_add_post_image.cpp#L203-L205&lt;/a&gt;&#160;&lt;/p&gt;

&lt;p&gt;i.e., if I do:&lt;/p&gt;

&lt;p&gt;t1: insert, t2: update, t3: delete&lt;/p&gt;

&lt;p&gt;and I read change stream for t2 after t3, the full doc will be null &#8211; is that expected when we say &quot;point-in-time&quot;? Or is there a way to get the post-image when the update actually happened at t2?&lt;/p&gt;</comment>
                            <comment id="4643883" author="JIRAUSER1262938" created="Tue, 28 Jun 2022 07:01:14 +0000"  >&lt;p&gt;Looks like it did &lt;a href=&quot;https://www.mongodb.com/docs/v6.0/changeStreams/#change-streams-with-document-pre--and-post-images&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.mongodb.com/docs/v6.0/changeStreams/#change-streams-with-document-pre--and-post-images&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="4643621" author="JIRAUSER1269994" created="Tue, 28 Jun 2022 01:58:15 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Did this make it into MongoDB 6.0?&lt;/p&gt;</comment>
                            <comment id="4526500" author="bernard.gorman" created="Wed, 4 May 2022 18:11:28 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=divanshu.aggarwal%40devrev.ai&quot; class=&quot;user-hover&quot; rel=&quot;divanshu.aggarwal@devrev.ai&quot;&gt;divanshu.aggarwal@devrev.ai&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;While we&apos;re not yet in a position to commit to a specific release date, we hope to make this feature available in MongoDB 6.0 on Atlas in June.&lt;/p&gt;

&lt;p&gt;Best regards,&lt;br/&gt;
Bernard&lt;/p&gt;</comment>
                            <comment id="4524943" author="JIRAUSER1268630" created="Wed, 4 May 2022 09:20:48 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Is there any time estimation of releasing this on MongoDb Atlas?&#160; Really a need for most of us for quite some time.&lt;/p&gt;</comment>
                            <comment id="4442339" author="bernard.gorman" created="Tue, 29 Mar 2022 16:23:39 +0000"  >&lt;p&gt;The feature requested in this ticket has now been completed, via a project spanning many other SERVER tickets, and will be available in MongoDB 6.0. Users will be able to request a point-in-time pre-image, a point-in-time post-image, or both. Users will also be able to enable or disable pre/post-image retention per-collection, and to specify for how long such pre- and post-images are retained.&lt;/p&gt;</comment>
                            <comment id="4442272" author="bernard.gorman" created="Tue, 29 Mar 2022 16:10:46 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ataramina%40shorecg.com&quot; class=&quot;user-hover&quot; rel=&quot;ataramina@shorecg.com&quot;&gt;ataramina@shorecg.com&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=william_luo%40trendmicro.com&quot; class=&quot;user-hover&quot; rel=&quot;william_luo@trendmicro.com&quot;&gt;william_luo@trendmicro.com&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=rupert.madden.abbott%40yellowdog.co&quot; class=&quot;user-hover&quot; rel=&quot;rupert.madden.abbott@yellowdog.co&quot;&gt;rupert.madden.abbott@yellowdog.co&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;To answer your questions:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;So the plan is to no longer include this feature in a 5.0 rapid release?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;This feature just missed the cut-off date for inclusion in the 5.3 rapid release. Our plan is therefore to make it available in the next scheduled release, which is MongoDB 6.0. Given the complexity of the feature, we don&apos;t plan to backport it to the 5.0.x release line.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;how is this going to interact with the 16MB limit? Let&apos;s say I have both &quot;before&quot; and &quot;fullDocument&quot; on. My change stream will now break if the original document is greater than 8MB?&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;If you request both the pre- and post-image in a scenario where your documents are large, it&apos;s possible that the resulting change stream event may exceed the 16MB limit. However, this limit only applies to documents as they exit the aggregation pipeline; documents that are still being processed within the pipeline can exceed it. You can therefore, for instance, apply a projection to the pre- and post-images to include only a subset of necessary fields, which will shrink the final output to below the 16MB limit.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Is this feature going to optionally include an &quot;after&quot; as well as a &quot;before&quot;? ... I can see it would be possible to add something downstream that merged the before with the updated/removed fields but I think this could get quite complicated, and it would be nicer to have something more out of the box!&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Yes! You will be able to request a point-in-time pre-image, a point-in-time post-image, or both.&lt;/p&gt;

&lt;p&gt;Thanks for your continued interest in this feature - we hope you&apos;ll be very pleased with the final result.&lt;/p&gt;

&lt;p&gt;Best regards,&lt;br/&gt;
Bernard&lt;/p&gt;</comment>
                            <comment id="4371249" author="JIRAUSER1265109" created="Wed, 23 Feb 2022 13:45:21 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Is this feature going to optionally include an &quot;after&quot; as well as a &quot;before&quot;?&lt;/p&gt;

&lt;p&gt;Currently, update &quot;fullDocuments&quot; are not necessarily accurate if any other operation interleaves before the lookup. It would be useful to avoid the need for that lookup.&lt;/p&gt;

&lt;p&gt;I can see it would be possible to add something downstream that merged the before with the updated/removed fields but I think this could get quite complicated, and it would be nicer to have something more out of the box!&lt;/p&gt;

&lt;p&gt;Also, how is this going to interact with the 16MB limit? Let&apos;s say I have both &quot;before&quot; and &quot;fullDocument&quot; on. My change stream will now break if the original document is greater than 8MB?&lt;/p&gt;

&lt;p&gt;We would also love this feature to be available in 5 if possible!&lt;/p&gt;</comment>
                            <comment id="4370921" author="JIRAUSER1260381" created="Wed, 23 Feb 2022 10:13:09 +0000"  >&lt;p&gt;I was disappointed to hear this too. Wish to see this available on 5.0 rapid release.&lt;/p&gt;</comment>
                            <comment id="4367117" author="JIRAUSER1269401" created="Mon, 21 Feb 2022 18:02:59 +0000"  >&lt;p&gt;So the plan is to no longer include this feature in a 5.0 rapid release?&#160; That is a bit disappointing, since this is something that we would like to see as well, and sooner rather than later.&lt;/p&gt;</comment>
                            <comment id="4350427" author="bernard.gorman" created="Fri, 11 Feb 2022 15:19:07 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=oraiches%40zadarastorage.com&quot; class=&quot;user-hover&quot; rel=&quot;oraiches@zadarastorage.com&quot;&gt;oraiches@zadarastorage.com&lt;/a&gt; - while we&apos;re not in a position to commit to an exact release timeline yet, our current plan is to deliver this feature in MongoDB 6.0.&lt;/p&gt;</comment>
                            <comment id="4332801" author="JIRAUSER1264630" created="Thu, 3 Feb 2022 12:33:25 +0000"  >&lt;p&gt;Would be happy to see this coming as well, is there any update on time estimation of releasing this?&lt;/p&gt;</comment>
                            <comment id="4296353" author="JIRAUSER1264414" created="Mon, 17 Jan 2022 18:24:09 +0000"  >&lt;p&gt;Very happy to see that this is being worked on! We&apos;re in the process of a significant re-architecture and this functionality is very important for us, both for updates and deletions.&lt;/p&gt;

&lt;p&gt;Being able to see the old values after updating a document in MongoDB would be perfect as we can then use this to clear old values from caches, instead of having to resort to saving old values in a separate field&lt;/p&gt;</comment>
                            <comment id="4193566" author="bernard.gorman" created="Tue, 16 Nov 2021 23:06:15 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=geotzinos%40gmail.com&quot; class=&quot;user-hover&quot; rel=&quot;geotzinos@gmail.com&quot;&gt;geotzinos@gmail.com&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;I&apos;m very pleased to tell you that we are in the middle of implementing this feature at present, and we expect it to be available in an upcoming Rapid Release version of MongoDB prior to the 6.0 LTS release (please &lt;a href=&quot;https://www.mongodb.com/blog/post/new-quarterly-releases-starting-with-mongodb-5-0&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;see here for more information about our Rapid Release schedule&lt;/a&gt;). Once this project is complete, change streams will be able to retrieve point-in-time pre-images and/or post-images for any collection on which the feature is enabled.&lt;/p&gt;

&lt;p&gt;Hope this helps!&lt;/p&gt;

&lt;p&gt;Best regards,&lt;br/&gt;
Bernard&lt;/p&gt;</comment>
                            <comment id="4192744" author="geotzinos@gmail.com" created="Tue, 16 Nov 2021 18:33:52 +0000"  >&lt;p&gt;Hello everyone! This is a really urgent need for most of us, any update on this?&lt;/p&gt;</comment>
                            <comment id="3917556" author="stany@q4inc.com" created="Tue, 6 Jul 2021 11:30:00 +0000"  >&lt;p&gt;Any update based on @Giambattista&apos;s comment?&#160;&lt;/p&gt;</comment>
                            <comment id="3911963" author="JIRAUSER1258206" created="Thu, 1 Jul 2021 12:58:12 +0000"  >&lt;p&gt;Since&#160;&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-45806&quot; title=&quot;Record pre-images on updates and deletes when recordPreImage is enabled&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-45806&quot;&gt;&lt;del&gt;SERVER-45806&lt;/del&gt;&lt;/a&gt; has been close and pre-image can be made available in the op-log, now it should be possible to make available pre-image information in the stream API. Pre-image is not only useful and nice feature: it indeed allow to use watch API as a proper Change Data Capture event stream with full document information. The current API exposes throttling when fetching full document content when multiple updates are executed shortly. Worst case is when updated is immediately followed by a delete event: in that case with current API could be not possible to fetch the full document when processing the update event.&lt;/p&gt;

&lt;p&gt;Also, it would be nice to have an helper method that reconstruct the resulting document given the pre-image and the update operation.&lt;/p&gt;</comment>
                            <comment id="2402043" author="james.blackhurst" created="Fri, 30 Aug 2019 16:19:44 +0000"  >&lt;p&gt;Being able to request `fullDocument` for delete events would be useful in conjunction with TTL indexes, where documents being expired out of the database (deleted) could be picked up by a change stream and archived in another storage solution.&#160;&lt;/p&gt;</comment>
                            <comment id="2377782" author="ben.perlmutter" created="Mon, 19 Aug 2019 19:24:58 +0000"  >&lt;p&gt;Hi Asya - the thought is that if Change Streams gave the previous state of the document, all the info desired would be in the change stream event.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Since it isn&apos;t there, they&apos;ll have to find the document and then perform the change and capture the flow on this end. While findAndModify doesn&apos;t incur an extra read (update needs to find the document, then update) - it does mean the developer flow to capture the change will need to be built on the update side (not the change streams side) and thus, the capturing of the change will incur a read on update (rather than read of the change streams event).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="1349703">SERVER-48186</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="601040">SERVER-37040</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="772208">SERVER-41236</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="1117840">SERVER-45806</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="790973">SERVER-41559</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="1808790">SERVER-58272</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="1678769">SERVER-56074</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>22.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <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_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[500A000000bw29LIAQ, 5002K00000fNe6iQAC, 5002K00000jdlsgQAA, 5002K00000nmg1nQAA, 5002K00000nnNebQAE, 5002K00000pCiVZQA0, 5002K00000pGPx5QAG, 5002K00000tRmDuQAK, 5002K00000vg4PqQAI, 5002K00000wWKZQQA4, 5002K00000zfjCPQAY, 5002K000012PzwUQAS]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 31 Aug 2018 13:01:04 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        1 year, 18 weeks, 2 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></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_17050" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Downstream Team Attention</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16941"><![CDATA[Not Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PM-1944</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>false</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>luke.bonanomi@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            1 year, 18 weeks, 2 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>ataramina@shorecg.com</customfieldvalue>
            <customfieldvalue>schwerin@mongodb.com</customfieldvalue>
            <customfieldvalue>arnie.listhaus@mongodb.com</customfieldvalue>
            <customfieldvalue>ben.perlmutter@mongodb.com</customfieldvalue>
            <customfieldvalue>bernard.gorman@mongodb.com</customfieldvalue>
            <customfieldvalue>brian.gaeddert@getalma.com</customfieldvalue>
            <customfieldvalue>divanshu.aggarwal@devrev.ai</customfieldvalue>
            <customfieldvalue>geotzinos@gmail.com</customfieldvalue>
            <customfieldvalue>giambattista.bloisi@iongroup.com</customfieldvalue>
            <customfieldvalue>james.blackhurst@mongodb.com</customfieldvalue>
            <customfieldvalue>oraiches@zadarastorage.com</customfieldvalue>
            <customfieldvalue>p.kalugin@paralect.com</customfieldvalue>
            <customfieldvalue>rupert.madden.abbott@yellowdog.co</customfieldvalue>
            <customfieldvalue>stany@q4inc.com</customfieldvalue>
            <customfieldvalue>warren@snowdropsolutions.co.uk</customfieldvalue>
            <customfieldvalue>william_luo@trendmicro.com</customfieldvalue>
            <customfieldvalue>ywu@stripe.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hu6u1r:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|i02v2v:</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_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_22250" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Special Downgrade Instructions Required</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="23343"><![CDATA[Not Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hu6gb3:</customfieldvalue>

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