[ 
https://issues.apache.org/jira/browse/TAJO-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944488#comment-14944488
 ] 

ASF GitHub Bot commented on TAJO-1877:
--------------------------------------

GitHub user dkhwangbo opened a pull request:

    https://github.com/apache/tajo/pull/808

    TAJO-1877: Adopt try-resource statement to AbstractDBStore

    See 
https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html.
 
    JDK 7 introduced try-resource statement for better resource allocation and 
deallocation. 
    We can also adopt this feature to AbstractDBStore.

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

    $ git pull https://github.com/dkhwangbo/tajo TAJO-1877

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

    https://github.com/apache/tajo/pull/808.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 #808
    
----
commit dbd422137c90feae029d6130620229156477000d
Author: Dongkyu Hwangbo <[email protected]>
Date:   2015-10-06T04:39:41Z

    initial commit

commit fb8d3ff5bc374ec2fa6b58b728921775fed4a85d
Author: Dongkyu Hwangbo <[email protected]>
Date:   2015-10-06T04:41:03Z

    remove unused import

----


> Adopt try-resource statement to AbstractDBStore
> -----------------------------------------------
>
>                 Key: TAJO-1877
>                 URL: https://issues.apache.org/jira/browse/TAJO-1877
>             Project: Tajo
>          Issue Type: Sub-task
>          Components: Catalog
>            Reporter: Hyunsik Choi
>            Assignee: Dongkyu Hwangbo
>              Labels: newbie
>
> See 
> https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html.
>  JDK 7 introduced try-resource statement for better resource allocation and 
> deallocation. We can also adopt this feature to AbstractDBStore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to