wud-if opened a new issue, #13454: URL: https://github.com/apache/gluten/issues/13454
### Description ### Motivation `CURRENT_DATE` and `CURRENT_TIME` are the session-timezone date/time expressions in Flink SQL. Today gluten-flink does not map them, so any query projecting them fails function offload (`Function not supported`) and stays on the native path. ### Proposal Offload them to the velox flinksql function set: - **velox side** (companion PR): session-timezone implementations under `velox/functions/flinksql/` — `CURRENT_DATE` returns the epoch-day date under the session time zone (read from `QueryConfig::sessionTimezone`); `CURRENT_TIME` returns the **millisecond-of-day INT** — the same encoding Flink `RowData` uses for TIME — so the bridge maps Flink `TIME` onto velox `INTEGER` and the value crosses unchanged. Both read the clock per row, matching streaming-mode Flink evaluation. - **planner side** (this repo): plain name mappings for `CURRENT_DATE` / `CURRENT_TIME`; `LogicalTypeConverter` maps `TimeType` onto velox `IntegerType` (the physical encoding alignment); TIME literals convert to the millisecond-of-day `IntegerValue`. Also fixes `VeloxQueryConfig`: Flink's `local-time-zone` `default` means the JVM default timezone, not UTC — without this, CURRENT_DATE / CURRENT_TIME diverge from native Flink across midnight. - Semantics to preserve: session-timezone resolution, per-record evaluation in streaming mode, TIME precision ceiling (millisecond), null propagation for TIME literals. **Gluten version**: main branch (gluten-flink) ### Gluten version None -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
