Hi there, friggin' amazing Pinot community! (Sorry...
# troubleshooting
d
Hi there, friggin' amazing Pinot community! (Sorry for the words, I'm just way too excited with this thing... hahaha) I'm having a bit of an issue with timestamps; I'm publishing data to Pinot with millisecond timestamps (since Epoch), but when I try to convert with
toDateTime
I'm getting unexpected times, like 7 hours ago. When I saw this, I thought it was an issue with the published timestamps, but then I fetched some data without doing the conversion, then I pasted a timestamp in my Python shell, converted it to a timezone-naive datetime object, and there it's just fine, it's the expected datetime. I tried to use
'UTC'
as the third argument for
toDateTime
, but to no avail, it still brings me the wrong datetime. This is not a super critical issue, since the vast majority of the analyses we'll do will be based off of a Python application, where that conversion will be done, but still, it would be nice to get more expected values right out of the Controller web UI. Any ideas what I can do to achieve that? [SOLVED] I was mistakenly using
hh
to convert the hours, while I should be using
HH
instead
For example, timestamp
1643839118403
gives me
2022-02-02 09:58:38
in Pinot, but
2022-02-02T18:58:38
in Python - the later of which is what I expected
Geez... sorry, nevermind, my bad, I was using
hh
to convert the hours instead of
HH
šŸ˜„
k
Nothing like posting a question and answering it yourself šŸ™‚
m
Haha, I love it when I am little late in responding and @Diogo Baeder’s monologue posts the question and answer.
d
Sorry guys... Hahaha
šŸ· 3