<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 09:05:30 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-70] Source Connector supports startAtOperationTime</title>
                <link>https://jira.mongodb.org/browse/KAFKA-70</link>
                <project id="16285" key="KAFKA">Kafka Connector</project>
                    <description>&lt;p&gt;The Source Connector should support the option startAtOperationTime to start watching a change stream at a certain point in time (assuming that the oplog is still available).&lt;/p&gt;

&lt;p&gt;Docs: &lt;a href=&quot;https://docs.mongodb.com/manual/changeStreams/#start-time&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.mongodb.com/manual/changeStreams/#start-time&lt;/a&gt; &lt;/p&gt;</description>
                <environment></environment>
        <key id="940968">KAFKA-70</key>
            <summary>Source Connector supports startAtOperationTime</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="christian.kurze@mongodb.com">Christian Kurze</reporter>
                        <labels>
                    </labels>
                <created>Thu, 26 Sep 2019 05:56:57 +0000</created>
                <updated>Mon, 25 Jul 2022 14:28:13 +0000</updated>
                            <resolved>Tue, 29 Mar 2022 13:37:38 +0000</resolved>
                                    <version>0.2</version>
                                                                        <votes>5</votes>
                                    <watches>10</watches>
                                                                                                                <comments>
                            <comment id="4441557" author="robert.walters" created="Tue, 29 Mar 2022 13:37:38 +0000"  >&lt;p&gt;The use cases backing this request are around data replication.&#160; These customers have either moved to a different solution or are beta testing cluster to cluster replication.&#160; For this reason we are not going to fix this.&#160;&#160;&lt;/p&gt;</comment>
                            <comment id="4129063" author="robert.walters" created="Mon, 18 Oct 2021 12:34:51 +0000"  >&lt;p&gt;Scheduled for 1.8&lt;/p&gt;</comment>
                            <comment id="3209537" author="christian.kurze" created="Tue, 16 Jun 2020 10:47:51 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=ross.lawley&quot; class=&quot;user-hover&quot; rel=&quot;ross.lawley&quot;&gt;ross.lawley&lt;/a&gt; I agree with the limitations, we discussed the approach in combination with &lt;a href=&quot;https://jira.mongodb.org/projects/KAFKA/issues/KAFKA-51&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://jira.mongodb.org/projects/KAFKA/issues/KAFKA-51&lt;/a&gt;. So there has to be governance around it that the oplog slice still exists and the replication can keep up with the changes. In the discussed case, the operation timestamp is taken form a process (can be custom code, backup restore, or something else) and starts the replication of events after the operation timestamp. Due to idempotent characteristics of the oplog, there can be an overlap into the past, but that depends on the use case and the characteristics of the sink.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="1062805">KAFKA-77</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[5002K00000e6tEqQAI, 5002K00000nmQQeQAM]]]></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|hr3ni7:</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>