[
https://issues.apache.org/jira/browse/DRILL-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844730#comment-13844730
]
Jacques Nadeau commented on DRILL-319:
--------------------------------------
There are a number of complexities here for a couple of reasons:
- This is integrated into the runtime compilation and we should be creating or
throw exceptions at this level.
- The logic for what should happen on warning, error, etc needs to be managed
throughout the expression tree. Expression trees have different sets of
outputs depending on their use so we need to figure out the right way to return.
- We should likely be avoiding object creation for this, especially if we
situations where we might generate 100s of millions of warnings or errors but
continue.
Rohit, would love to hear your thoughts on design for solving these problems.
> Drill function need specify how to handle error.
> -------------------------------------------------
>
> Key: DRILL-319
> URL: https://issues.apache.org/jira/browse/DRILL-319
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Jinfeng Ni
>
> Currently, drill's built-in function will raise Exception when it catches
> one, and stops the execution immediately.
> Depending on the nature of the function or the query, we might need allow
> function behaviors differently :
> -- Issue SQL Error code, and stop the execution.
> -- Issue SQL warning, continue the execution for the next row.
> -- Continue the execution for the next row, and log the # of error /
> warning for user awareness.
> Therefore, we need have a way to specify the different strategy how to handle
> error for different function implementation, for either build-in function, or
> UDF.
>
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
