[
https://issues.apache.org/jira/browse/DRILL-5512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015231#comment-16015231
]
ASF GitHub Bot commented on DRILL-5512:
---------------------------------------
Github user sohami commented on a diff in the pull request:
https://github.com/apache/drill/pull/838#discussion_r117161761
--- Diff: protocol/src/main/protobuf/UserBitShared.proto ---
@@ -74,16 +74,22 @@ message DrillPBError{
*/
RESOURCE = 7;
/* equivalent to SQLNonTransientException.
+ * - out of memory
--- End diff --
for out of memory we throw "memoryError" which internally set's the
errorType as RESOURCE not SYSTEM.
> Standardize error handling in ScanBatch
> ---------------------------------------
>
> Key: DRILL-5512
> URL: https://issues.apache.org/jira/browse/DRILL-5512
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.10.0
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Priority: Minor
> Fix For: 1.10.0
>
>
> ScanBatch is the Drill operator executor that handles most readers. Like most
> Drill operators, it uses an ad-hoc set of error detection and reporting
> methods that evolved over Drill development.
> This ticket asks to standardize on error handling as outlined in DRILL-5083.
> This basically means reporting all errors as a {{UserException}} rather than
> using the {{IterOutcome.STOP}} return status or using the
> {{FragmentContext.fail()}} method.
> This work requires the new error codes introduced in DRILL-5511, and is a
> step toward making readers aware of vector size limits.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
