drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] paul-rogers commented on issue #1455: DRILL-6724: Convert IndexOutOfBounds exception to UserException with …
Date Tue, 04 Sep 2018 18:11:05 GMT
paul-rogers commented on issue #1455: DRILL-6724: Convert IndexOutOfBounds exception to UserException
with …
URL: https://github.com/apache/drill/pull/1455#issuecomment-418465629
 
 
   @arina-ielchiieva, very good point. Having that information is very useful regardless of
the source of error. How could we provide that generically without the need to wrap each bit
of code in a "in case something goes wrong" try/catch block? For example, suppose we get an
NPE or OOM. Should we catch all those?
   
   Could each operator (including scanners) provide a context which can be dumped to the log
along with the stack trace? Often, we try to recreate the fragment operators from the stack
trace. Would be better to see a stack of operators, each with it's critical info.
   
   The fragment exec walks the operator tree to shut down each operator. I could also do so
to create the operator stack with related info.
   
   Is this something we could consider? Would have been very helpful the many times I tried
to track down a failure found in a QA test or user case.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message