[
https://issues.apache.org/jira/browse/CALCITE-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17838087#comment-17838087
]
Claude Brisson commented on CALCITE-6371:
-----------------------------------------
We're speaking about literals, here. A perfectly legitimate policy can be to
consider {{1/0}} as an invalid literal, and to refuse to process a query
containing it, even if its evaluation can somehow be evicted down the line.
> Add ability to configure RexExecutable behavior on exceptions
> -------------------------------------------------------------
>
> Key: CALCITE-6371
> URL: https://issues.apache.org/jira/browse/CALCITE-6371
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.36.0
> Reporter: Claude Brisson
> Priority: Major
>
> The current behavior of Calcite's {{RexExecutable}} constant folding class is
> to eat all exceptions encountered during reduction. The underlying reason, as
> far as I understand it, is that even if Calcite can't reduce an expression,
> maybe the evaluation engine will be able to do it. Fair enough.
> But it would be useful to be able to chose to let some exceptions go through.
> One good example is {{ArithmeticException}} errors. They occur on divisions
> by zero, negative logarithms, etc. and we may want to avoid the downstream
> evaluation engine to receive such invalid expressions.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
