[
https://issues.apache.org/jira/browse/DRILL-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957501#comment-14957501
]
ASF GitHub Bot commented on DRILL-3927:
---------------------------------------
Github user jacques-n commented on the pull request:
https://github.com/apache/drill/pull/199#issuecomment-148153599
I'm against having a caught exception for OutOfMemory. This should be a
RuntimeException since it can happen anywhere. Why did you choose to use this
instead of the Runtime version?
> Use OutOfMemoryException in more places
> ---------------------------------------
>
> Key: DRILL-3927
> URL: https://issues.apache.org/jira/browse/DRILL-3927
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: Chris Westin
> Assignee: Chris Westin
>
> The new allocator uses OutOfMemoryException in better ways; some additional
> exception handling sites need to catch and handle this exception in
> preparation for the new allocator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
