[cloud/v3] Casting BIGINT to TIMESTAMP doesn't seem to work anymore

[Notilarie]

Steps to reproduce:
List the minimal actions needed to reproduce the behaviour.

1. Open data explore on InfluxDB Cloud
2. Execute the folowing query: SELECT 1705590600000000000::TIMESTAMP

Expected behaviour:
I would expect a timestamp

Actual behaviour:
An exception is thrown:
Error while planning query: Optimizer rule 'simplify_expressions' failed
caused by
Arrow error: Compute error: Overflow happened on: 1705590600000000000 * 1000000000: rpc error: code = InvalidArgument desc = Error while planning query: Optimizer rule 'simplify_expressions' failed
caused by
Arrow error: Compute error: Overflow happened on: 1705590600000000000 * 1000000000

Environment info:

• InfluxDB Cloud

As workaround I use the following query:
SELECT 1705590600000000000::BIGINT UNSIGNED::TIMESTAMP

On older versions of InfluxDB, unsigned big ints are not allowed to cast to timestamp

[philjb]

@btasker - this is reported as a issue in cloud serverless.

[btasker]

This looks like a SQL issue (it's being run via the Cloud UI which doesn't accept InfluxQL) so doesn't fall under my purview.

I've flagged up internally.

[helenosheaa]

The Cloud UI does accept InfluxQL as well these days but anyway I think the problem is probably coming from InfluxQL-IOx, when direct casting an integer using ::timestamp IOx will default to treat it as seconds (we will work on fixing this)

@NotiArie Workaround in the meantime would be to use to_timestamp_seconds or to_timestamp_mills etc to explicitly specify the precision to use.