GitHub user cwestin opened a pull request:

    https://github.com/apache/drill/pull/199

    DRILL-3927: use OutOfMemoryException in more places

    Some code cleanup required for the upcoming introduction of the rewritten
    direct memory allocator. Chiefly the introduction of OutOfMemoryException
    handling in a few spots, the use of DrillAutoCloseables for some allocator
    close() calls, and some other minor cleanup.
    - removed the exclusion of exec/work from the jdbc-all jar, because it now
      depends on OutOfMemoryException, and that is derived from
      FragmentSetupException and Foreman Exception
    
    Unit tests pass
    Regression suite passes, except for
    - a couple of the known "Exceeded timeout (10000) while waiting send 
intermediate work fragments to remote nodes."
    - a couple of the known "Selected column 'dir0' must have name 'columns' or 
must be plain '*'"

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cwestin/incubator-drill hygiene-gamma

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/199.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #199
    
----
commit e7e95a261523846617e62880fdb9a20448ac818c
Author: Chris Westin <[email protected]>
Date:   2015-10-09T21:08:09Z

    DRILL-3927: use OutOfMemoryException in more places
    Some code cleanup required for the upcoming introduction of the rewritten
    direct memory allocator. Chiefly the introduction of OutOfMemoryException
    handling in a few spots, the use of DrillAutoCloseables for some allocator
    close() calls, and some other minor cleanup.
    - removed the exclusion of exec/work from the jdbc-all jar, because it now
      depends on OutOfMemoryException, and that is derived from
      FragmentSetupException and Foreman Exception

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to