Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
cannot_touch
Contributor II
Contributor II

Replace timestamp in replication task

Hello, 

we are using Qlik Replicate to send date from a db2 database to Apace Kafka. In the Kafka topics we noticed that the timestamp in the head section is 2 hours off from what we would expect. Is there a way to configure the replication task in a way so that it adds 2 hours to that timestamp? 

Do you have any idea why the timestamp behaves that way? On our systems the time is configured correctly.

 

cannot_touch_0-1653922407766.png

 

Labels (1)
1 Solution

Accepted Solutions
SwathiPulagam
Support
Support

Hi @cannot_touch ,

  The timestamp which shows in the Kafka message is Source commit timestamp in UTC format and you can't change it in replicate settings. Please verify and confirm the timestamp is in UTC format.

Thanks,

Swathi

View solution in original post

3 Replies
SwathiPulagam
Support
Support

Hi @cannot_touch ,

  The timestamp which shows in the Kafka message is Source commit timestamp in UTC format and you can't change it in replicate settings. Please verify and confirm the timestamp is in UTC format.

Thanks,

Swathi

Heinvandenheuvel
Specialist III
Specialist III

The header column Timestamp is document to be "String The original change UTC timestamp." So no you cannot change that.

What is the timezone the DB is living in?

You are free to use a Transformation to ADD a Column perhaps called 'AdjustedTimestamp' or 'LocalTimestamp' where you use a transformtion which adds 2 hours using the "+2 hours" modifiers. Please check the SQLite documentation and search for other examples and usages in this forum.

https://www.sqlite.org/lang_datefunc.html - Modifiers, Examples.

Hein

 

cannot_touch
Contributor II
Contributor II
Author

@Heinvandenheuvel @SwathiPulagam thanks for your replies. Your are correct it looks like it is UTC. I will check the timezone for the db2 server. Thank you.