Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Support Team,
There are 「Advanced Run Options」 available for Qlik tasks.
You can select the following in 「Tables are already loaded. Start processing changes from:」.
・Date and Time
・Source change position
In the REST API RunTask there is an option "RESUME_PROCESSING_FROM_TIMESTAMP",
I think this is the same function as 「Date and Time」.
Please tell me how to specify 「Source change position」 as a RunTask option.
Hello @iti-attunity-sup ,
Thank you for reaching out to the Qlik Community!
From the Replicate UI, Using SCN.LSN it is working as expected.
However, the problem is when trying to do the same, using the REST APIs:
- The RunTask API service includes the cdcposition in the Body, and there are 2 options supported:
{"cdcposition":"timestamp"}
Example: {"cdcposition":"2017-03-07T11:19:03"}
{"cdcposition":"target_checkpoint"}
Example: {"cdcposition":"Checkpoint:V1#1#timestamp:2017-02-14T12:34:44#0#0#*#0#0"}
- The issue is that the REST API service does not support including a stream position (SCN, LSN, etc), to do this programmatically:
We would request you to create ideation request. "https://community.qlik.com/t5/Suggest-an-Idea/Start-child-logStream-tasks-from-change-position-0-via...
in order to support this.
Hope the above information is helpful
If the provided above information helps, please "Accept as Solution".
Regards,
Sachin B
>> I found out that I cannot specify LSN in RESUME of REST API.
I suspect you can, but have not found a documented example. I think I remember I seeing one.
If I recall correctly the Replicate MS SQL log reader utilities allowed 'now', 'timestamp:' and 'lsn:' but admittedly the AEM API seems to use a naked timestamp not timestamp:xxx. Maybe I remember it working just with the Replicate GUI and/or repctl commandline?
Hein.
try {"cdcposition":"lsn:xxx"} ??
Hello @iti-attunity-sup ,
Thank you for reaching out to the Qlik Community!
From the Replicate UI, Using SCN.LSN it is working as expected.
However, the problem is when trying to do the same, using the REST APIs:
- The RunTask API service includes the cdcposition in the Body, and there are 2 options supported:
{"cdcposition":"timestamp"}
Example: {"cdcposition":"2017-03-07T11:19:03"}
{"cdcposition":"target_checkpoint"}
Example: {"cdcposition":"Checkpoint:V1#1#timestamp:2017-02-14T12:34:44#0#0#*#0#0"}
- The issue is that the REST API service does not support including a stream position (SCN, LSN, etc), to do this programmatically:
We would request you to create ideation request. "https://community.qlik.com/t5/Suggest-an-Idea/Start-child-logStream-tasks-from-change-position-0-via...
in order to support this.
Hope the above information is helpful
If the provided above information helps, please "Accept as Solution".
Regards,
Sachin B
Hi Sachin B san,
Thank you for your reply.
I found out that I cannot specify LSN in RESUME of REST API.
Thank you.
Best Regards,
Sato
>> I found out that I cannot specify LSN in RESUME of REST API.
I suspect you can, but have not found a documented example. I think I remember I seeing one.
If I recall correctly the Replicate MS SQL log reader utilities allowed 'now', 'timestamp:' and 'lsn:' but admittedly the AEM API seems to use a naked timestamp not timestamp:xxx. Maybe I remember it working just with the Replicate GUI and/or repctl commandline?
Hein.
try {"cdcposition":"lsn:xxx"} ??
Hi Hein san,
thank you for your reply.
I need to specify REST API options, but what should I specify?
For "Date and Time", it will be "RESUME_PROCESSING_FROM_TIMESTAMP".
Best Regards,
Sato