<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:14:21 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>[DOCS-15996] [SERVER] Investigate changes in SERVER-72486: Expand the set of queries eligible for SBE in the 7.0 release</title>
                <link>https://jira.mongodb.org/browse/DOCS-15996</link>
                <project id="10380" key="DOCS">Documentation</project>
                    <description>    &lt;div class=&quot;panel&quot; style=&quot;background-color: #c2d2c2;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelHeader&quot; style=&quot;border-bottom-width: 1px;background-color: #239eb0;&quot;&gt;&lt;b&gt;Original Downstream Change Summary&lt;/b&gt;&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;    This change enables additional scenarios in the slot-based execution engine (SBE), the new query execution engine that the query execution team has been working on for the last few years. The SBE engine was enabled in a limited way in 6.0 but was first broadly enabled in 6.3 under &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-71798&quot; title=&quot;Expand the set of queries eligible for SBE in the 6.3 release&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-71798&quot;&gt;&lt;del&gt;SERVER-71798&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;This change goes further and enables even more scenarios in SBE for the 7.0 LTS release. The change in execution engine should be largely transparent to applications and end-users. However, given the scope of the changes between Classic and SBE, performance differences are possible. (For the most part SBE in 7.0 is a faster engine when compared to the Classic Engine.)&lt;/p&gt;

&lt;p&gt;The fact that SBE is being used under the hood will show up in the server&apos;s debug mechanisms, which is the main reason that I&apos;ve marked this as needing downstream attention. In particular, the explain output will look substantially different for SBE. Explain output for queries using the classic engine report explainVersion:&quot;1&quot; whereas explain output for queries using SBE report explainVersion:&quot;2&quot;.&lt;/p&gt;

&lt;p&gt;There are also some differences in debug output produced by $planCacheStats as well as changes in system.profile and slow query log lines (e.g. an indication that SBE was the engine used).&lt;/p&gt;
&lt;h2&gt;&lt;a name=&quot;DescriptionofLinkedTicket&quot;&gt;&lt;/a&gt;Description of Linked Ticket&lt;/h2&gt;
&lt;p&gt;    This is the same as &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-71798&quot; title=&quot;Expand the set of queries eligible for SBE in the 6.3 release&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-71798&quot;&gt;&lt;del&gt;SERVER-71798&lt;/del&gt;&lt;/a&gt;, but for 7.0.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="2302947">DOCS-15996</key>
            <summary>[SERVER] Investigate changes in SERVER-72486: Expand the set of queries eligible for SBE in the 7.0 release</summary>
                <type id="3" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14718&amp;avatarType=issuetype">Task</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="3">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="backlog-server-pm">Backlog - Core Eng Program Management Team</reporter>
                        <labels>
                    </labels>
                <created>Thu, 30 Mar 2023 21:37:26 +0000</created>
                <updated>Mon, 13 Nov 2023 17:34:18 +0000</updated>
                            <resolved>Thu, 27 Jul 2023 19:10:48 +0000</resolved>
                                                    <fixVersion>7.0.0-rc0</fixVersion>
                    <fixVersion>Server_Docs_20231030</fixVersion>
                    <fixVersion>Server_Docs_20231106</fixVersion>
                    <fixVersion>Server_Docs_20231105</fixVersion>
                    <fixVersion>Server_Docs_20231113</fixVersion>
                                    <component>manual</component>
                    <component>Server</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="5596536" author="JIRAUSER1263037" created="Thu, 27 Jul 2023 19:10:48 +0000"  >&lt;p&gt;Closing as a duplicate of DOCSP-30502. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10320">
                    <name>Documented</name>
                                            <outwardlinks description="documents">
                                        <issuelink>
            <issuekey id="2223082">SERVER-72486</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 27 Jul 2023 19:10:48 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        27 weeks, 6 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_17052" key="com.atlassian.jira.plugin.system.customfieldtypes:textarea">
                        <customfieldname>Downstream Changes Summary</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>This change enables additional scenarios in the slot-based execution engine (SBE), the new query execution engine that the query execution team has been working on for the last few years. The SBE engine was enabled in a limited way in 6.0 but was first broadly enabled in 6.3 under &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-71798&quot; title=&quot;Expand the set of queries eligible for SBE in the 6.3 release&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-71798&quot;&gt;&lt;strike&gt;SERVER-71798&lt;/strike&gt;&lt;/a&gt;.&lt;br/&gt;
&lt;br/&gt;
This change goes further and enables even more scenarios in SBE for the 7.0 LTS release. The change in execution engine should be largely transparent to applications and end-users. However, given the scope of the changes between Classic and SBE, performance differences are possible. (For the most part SBE in 7.0 is a faster engine when compared to the Classic Engine.)&lt;br/&gt;
&lt;br/&gt;
The fact that SBE is being used under the hood will show up in the server&amp;#39;s debug mechanisms, which is the main reason that I&amp;#39;ve marked this as needing downstream attention. In particular, the explain output will look substantially different for SBE. Explain output for queries using the classic engine report explainVersion:&amp;quot;1&amp;quot; whereas explain output for queries using SBE report explainVersion:&amp;quot;2&amp;quot;.&lt;br/&gt;
&lt;br/&gt;
There are also some differences in debug output produced by $planCacheStats as well as changes in system.profile and slow query log lines (e.g. an indication that SBE was the engine used).</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>emet.ozar@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            27 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>backlog-server-pm</customfieldvalue>
            <customfieldvalue>kenneth.dyer@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i22p4v:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|i1l1kw:</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_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i22ba7:</customfieldvalue>

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