This message was deleted.

I think it’s because the __time column is empty on some rows. But why we didn’t see this on 0.22.1?

Just a thought, what happens if you cast the literal date value to a timestamp?

coalesce works. I think in general the SQL engine is becoming more strict and I think that's a good thing. 👍

hmm. this was fixed in https://github.com/apache/druid/pull/12834

Looks like a simple enough change to backport to our 0.23.0. What do you think?

Yeah it should be pretty straightforward if you wanted to backport it

call me crazy but ever since that 1 customer used COALESCE function, CPU spiked on all historicals.

I would never call you crazy 🙂 If you suspect something funny going on, you could try profiling one if your historicals and see what it spends its CPU time on