Question: what philosophy do you guys follow regar...
# singer-tap-development
s
Question: what philosophy do you guys follow regarding timestamps? I'm having issues where different replication keys in the same tap have different formats (YYYY-MM-DD; Datetime, Epoch, etc.). How do you deal with this issue when trying to impose state management in post process? Do you set everything to timestamp when parsing the response, or modify it only for the post process?
a
In state specifically, I think everything is a timestamp.
In tap schemas, I think we want to have good support for dates (timezone-less) as well as timestamps.
Does this help at all to answer your questions?
s
So if you received data in the form of an epoch, you would parse the response in the form of a datetime object?
a
Epoch I'm not sure. I think generally, this would get interpreted as a numeric and it may require casting.
(post_process() would be a good place to do this, if needed)
s
Alright, awesome. Would it be helpful if I made a PR to integrate support for epoch timestamps into meltano?