<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Re: Replicate - Add millisecond precision to Commit Timestamp (header column) for MongoDB Source in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1801751#M5972</link>
    <description>&lt;P&gt;Yes, we rely on&amp;nbsp;&lt;A href="https://docs.mongodb.com/manual/reference/change-events/" target="_blank"&gt;https://docs.mongodb.com/manual/reference/change-events/&lt;/A&gt;&amp;nbsp;- specifically clusterTime.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Apr 2021 12:46:58 GMT</pubDate>
    <dc:creator>Shelley_Brennan</dc:creator>
    <dc:date>2021-04-22T12:46:58Z</dc:date>
    <item>
      <title>Replicate - Add millisecond precision to Commit Timestamp (header column) for MongoDB Source</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idi-p/1785465</link>
      <description>&lt;P&gt;We are using Replicate with a MongoDB Source and an Oracle Target.&lt;/P&gt;&lt;P&gt;We would really like the AR_H_COMMIT_TIMESTAMP/AR_H_TIMESTAMP header columns to be populated with a timestamp value that has greater precision than a second.&lt;/P&gt;&lt;P&gt;Other sources populate those columns down to the millisecond, but it only goes down to the second with a MongoDB Source.&lt;/P&gt;&lt;P&gt;The MongoDB Oplog does contain a commit timestamp field that has the greater precision, but the current one that is being pulled from the Oplog only goes down to the second.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 18:59:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idi-p/1785465</guid>
      <dc:creator>Adam_Brillhart</dc:creator>
      <dc:date>2021-02-23T18:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - Add millisecond precision to Commit Timestamp (header column) for MongoDB Source - Status changed to: Open - Collecting Feedback</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1789215#M5422</link>
      <description>&lt;P&gt;Replicate relies on the official MongoDB Change Streams API which only reports on the commit timestamp down to the second, not millisecond.&amp;nbsp; It may be stored in the Oplog in milliseconds but Replicate is not designed to read directly from Oplog.&amp;nbsp; I would suggest opening a case with MongoDB support to see if they can expose the timestamp in milliseconds via the API at which point Replicate could report on the data you are looking for.&amp;nbsp; And we will raise this with MongoDB support as well on our side.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 13:54:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1789215#M5422</guid>
      <dc:creator>Shelley_Brennan</dc:creator>
      <dc:date>2021-03-08T13:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - Add millisecond precision to Commit Timestamp (header column) for MongoDB Source</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1798837#M5815</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/91649"&gt;@Shelley_Brennan&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi Shelley,&lt;/P&gt;&lt;P&gt;I was wondering if you could tell me the specific API call from from the MongoDB Change Streams API that is being used by Replicate to get that commit timestamp value?&lt;BR /&gt;I'm not sure if you have raised a MongoDB Support ticket yet, but we will use that info to raise a MongoDB Support ticket as well.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 15:14:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1798837#M5815</guid>
      <dc:creator>Adam_Brillhart</dc:creator>
      <dc:date>2021-04-12T15:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - Add millisecond precision to Commit Timestamp (header column) for MongoDB Source</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1801751#M5972</link>
      <description>&lt;P&gt;Yes, we rely on&amp;nbsp;&lt;A href="https://docs.mongodb.com/manual/reference/change-events/" target="_blank"&gt;https://docs.mongodb.com/manual/reference/change-events/&lt;/A&gt;&amp;nbsp;- specifically clusterTime.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 12:46:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/1801751#M5972</guid>
      <dc:creator>Shelley_Brennan</dc:creator>
      <dc:date>2021-04-22T12:46:58Z</dc:date>
    </item>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/2101218#M14462</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/274822" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 16:16:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/2101218#M14462</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T16:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate - Add millisecond precision to Commit Timestamp (header column) for MongoDB Source - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/2101219#M14463</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 16:16:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-Add-millisecond-precision-to-Commit-Timestamp-header/idc-p/2101219#M14463</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T16:16:33Z</dc:date>
    </item>
  </channel>
</rss>

