<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 09:06:10 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>[KAFKA-342] clusterTime field is missing in copy-existing events</title>
                <link>https://jira.mongodb.org/browse/KAFKA-342</link>
                <project id="16285" key="KAFKA">Kafka Connector</project>
                    <description>&lt;p&gt;Insert events that originate from a copy-existing process don&apos;t have a &lt;tt&gt;clusterTime&lt;/tt&gt; field as any other change events that don&apos;t originate from copy-existing.&#160;&lt;/p&gt;

&lt;p&gt;I think this field should be included in such events for the following reasons:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;It&apos;s an important metadata that identifies when the event originated and not including it doesn&apos;t make much sense in general. The event already has fields that identify it as an event that originated from a copy-existing process so it&apos;ll be clear to what event time the value refers.&lt;/li&gt;
&lt;/ol&gt;



&lt;ol&gt;
	&lt;li&gt;Without it, it&apos;s impossible to have idempotency upstream in case of multiple copy-existing runs.&lt;br/&gt;
For example, if copy-existing sent an insert event for _id=1 and then later additional events might be originated for _id=1 from the change stream or not but if eventually copy-existing process will have to be re-run due to losing the last offset or for any other reason, then it&apos;ll impossible to tell which of the two insert events from the copy-existing process is the latest one and whether it&apos;s before or after any other events for _id=1 that originated from change streams.&lt;br/&gt;
So currently, in such scenarios, we have to rely on events publishing order which is not a best practice in my opinion.&lt;/li&gt;
&lt;/ol&gt;
</description>
                <environment></environment>
        <key id="2189330">KAFKA-342</key>
            <summary>clusterTime field is missing in copy-existing events</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="13203">Gone away</resolution>
                                        <assignee username="robert.walters@mongodb.com">Robert Walters</assignee>
                                    <reporter username="alonp@accessfintech.com">Alon Prantsipal</reporter>
                        <labels>
                    </labels>
                <created>Fri, 18 Nov 2022 00:36:25 +0000</created>
                <updated>Fri, 27 Oct 2023 19:45:06 +0000</updated>
                            <resolved>Tue, 6 Dec 2022 12:00:59 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="5032890" author="dbeng-pm-bot" created="Tue, 6 Dec 2022 12:01:01 +0000"  >&lt;p&gt;There hasn&apos;t been any recent activity on this ticket, so we&apos;re resolving it. Thanks for reaching out! Please feel free to comment on this if you&apos;re able to provide more information.&lt;/p&gt;</comment>
                            <comment id="4997313" author="robert.walters" created="Mon, 21 Nov 2022 15:52:36 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=alonp%40accessfintech.com&quot; class=&quot;user-hover&quot; rel=&quot;alonp@accessfintech.com&quot;&gt;alonp@accessfintech.com&lt;/a&gt;, the copy existing process does not include any metadata for clusterTime.&#160; That said, in the next version of the Kafka Connector we are support start at operation time, basically the ability to start the source connector at a certain time in the oplog.&#160; (setting it to the value 0 will start at the beginning of the oplog).&#160; This option will include the clusterTime as it is reflected in the change stream event metadata.&#160; 1.9 should be out by mid-end of December.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                    </comments>
                    <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|i11q20:</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>