andygrove opened a new issue, #3336:
URL: https://github.com/apache/datafusion-comet/issues/3336
## Description
When Spark's `ConstantFolding` optimizer rule is disabled, all-scalar
(literal-only) expressions reach Comet's native engine instead of being folded
at plan time. The native engine panics with messages like:
- `hour(scalar) should be fold in Spark JVM side.`
- `minute(scalar) should be fold in Spark JVM side.`
- `second(scalar) should be fold in Spark JVM side.`
- `unix_timestamp(scalar) should be fold in Spark JVM side.`
## How to Reproduce
Disable constant folding and run an all-literal datetime extraction query:
```sql
SET
spark.sql.optimizer.excludedRules=org.apache.spark.sql.catalyst.optimizer.ConstantFolding;
SELECT hour(timestamp('2024-01-15 12:30:45'));
```
## Expected Behavior
The native engine should handle scalar inputs gracefully — either by
computing the correct result or by falling back to Spark, not by panicking.
## Affected Expressions
- `hour()`
- `minute()`
- `second()`
- `unix_timestamp()`
--
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]
