Druid shows "1970-01-01T00:00:00.000Z" with TIME_PARSE function even though the column should be NULL

[carltal]

Affected Version

The Druid version where the problem was encountered: 29.0.1

Description

Please see the screenshots below.

When we have the TIME_PARSE function in both SELECT and WHERE clauses, the output is correct; the column shows null.

When we DO NOT have time TIME_PARSE function in both SELECT and WHERE clauses, the output is also correct; the column shows null.

However, when we have TIME_PARSE function in SELECT but not in WHERE clause, the column shows "1970-01-01T00:00:00.000Z."

The column's type is VARCHAR.

We would like to report this finding to Druid developers. Thanks.

[abhishekagarwal87]

Do you have a sample data and ingestion spec that will allow us to reproduce this bug?

[LakshSingla]

#16915 might resolve this. I can confirm it in a while.

[carltal]

@abhishekagarwal87 Hi, thanks for your response. Unfortunately the above screenshot is all I can provide at this time.

[carltal]

@LakshSingla Thank you! Yes that looks to be the issue we are facing.