forked from docs/doc-exports
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: chenxiaoxiong <chenxiaoxiong@huawei.com> Co-committed-by: chenxiaoxiong <chenxiaoxiong@huawei.com>
19 lines
3.2 KiB
HTML
19 lines
3.2 KiB
HTML
<a name="dataartsstudio_01_0125"></a><a name="dataartsstudio_01_0125"></a>
|
||
|
||
<h1 class="topictitle1">MongoDB/DDS Incremental Migration</h1>
|
||
<div id="body8662426"><p id="dataartsstudio_01_0125__en-us_topic_0000001622495010_p28242048171110">By using CDM, you can export MongoDB or DDS data within a specified period. With the scheduled jobs of CDM, you can implement incremental migration of MongoDB and DDS.</p>
|
||
<div class="note" id="dataartsstudio_01_0125__en-us_topic_0000001622495010_note45791757134910"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dataartsstudio_01_0125__en-us_topic_0000001622495010_en-us_topic_0108275319_p52974484409">If you have configured a macro variable of date and time and schedule a CDM job through <span id="dataartsstudio_01_0125__en-us_topic_0000001622495010_en-us_topic_0108275319_text9997118203">DataArts Studio DataArts Factory</span>, the system replaces the macro variable of date and time with (<em id="dataartsstudio_01_0125__en-us_topic_0000001622495010_en-us_topic_0108275319_i799871152012">Planned start time of the data development job</em> – <em id="dataartsstudio_01_0125__en-us_topic_0000001622495010_en-us_topic_0108275319_i0998101192020">Offset</em>) rather than (<em id="dataartsstudio_01_0125__en-us_topic_0000001622495010_en-us_topic_0108275319_i299821132018">Actual start time of the CDM job</em> – <em id="dataartsstudio_01_0125__en-us_topic_0000001622495010_en-us_topic_0108275319_i129981917200">Offset</em>).</p>
|
||
</div></div>
|
||
<p id="dataartsstudio_01_0125__en-us_topic_0000001622495010_p1955674331710">When creating a table/file migration job and selecting the link to MongoDB or DDS as the source link, you can set the query filters in advanced attributes.</p>
|
||
<div class="fignone" id="dataartsstudio_01_0125__en-us_topic_0000001622495010_fig55241448173918"><span class="figcap"><b>Figure 1 </b>Setting query filters</span><br><span><img id="dataartsstudio_01_0125__en-us_topic_0000001622495010_image48701124296" src="en-us_image_0000002269197449.png"></span></div>
|
||
<p id="dataartsstudio_01_0125__en-us_topic_0000001622495010_p1217034714384"></p>
|
||
<p id="dataartsstudio_01_0125__en-us_topic_0000001622495010_p1815118591406">You can set this parameter to a <a href="dataartsstudio_01_0114.html">macro variable of date and time</a>, for example, <strong id="dataartsstudio_01_0125__en-us_topic_0000001622495010_b1237231673014">{"ts":{$gte:ISODate("${dateformat(yyyy-MM-dd'T'HH:mm:ss.SSS'Z',-1,DAY)}")}}</strong>, which indicates searching for the values in the <strong id="dataartsstudio_01_0125__en-us_topic_0000001622495010_b3197440174817">ts</strong> field that are greater than those after time macro conversion, that is, only the data generated after the previous day is exported.</p>
|
||
<p id="dataartsstudio_01_0125__en-us_topic_0000001622495010_p588931118499">After this parameter is set, CDM exports only the data generated on the previous day. In addition, you can set the job to be executed at 00:00:00 every day, so that the data generated every day can be incrementally synchronized.</p>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="dataartsstudio_01_0111.html">Incremental Migration</a></div>
|
||
</div>
|
||
</div>
|
||
|