Parseable incorrectly extracts stream name from query when using arrow datafusion extract

[stanvanrooy]

It is currently not possible to use the extract function because the syntax of it confuses Parseable. Can be easily reproduced by running the query below in the demo environment.

SELECT extract(epoch FROM p_timestamp) FROM backend

I'd be more than happy to contribute on a fix, if someone can point me in the right direction.

[nitisht]

Thanks for reporting @stanvanrooy we'll take a look and also see how you can help.

[trueleo]

@stanvanrooy I'll look into fixing this for upcoming release. The parsing for stream name is what is causing this issue. This stream name is used for file selection and query planning before query engine is run.

You may rewrite your query as follow so that the table name comes first.

WITH tab AS (
  SELECT * FROM backend
)
SELECT extract(epoch FROM p_timestamp)
FROM tab;

[stanvanrooy]

@trueleo thanks!