You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by rekhajoshm <gi...@git.apache.org> on 2017/04/06 18:51:20 UTC

[GitHub] beam pull request #2454: [BEAM-1832] Fix for potentially unclosed streams in...

GitHub user rekhajoshm opened a pull request:

    https://github.com/apache/beam/pull/2454

    [BEAM-1832] Fix for potentially unclosed streams in ApexYarnLauncher

    [BEAM-1832] Fix for potentially unclosed streams in ApexYarnLauncher
     - Using try-resources to handle closeable close issue
     - Removed redundant semicolons, string null assignment
     - Indent/spaces as per beam codestyle. Checkstyle passes. mvn clean verify passes.

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

    $ git pull https://github.com/rekhajoshm/beam BEAM-1832-0

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

    https://github.com/apache/beam/pull/2454.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 #2454
    
----
commit 46700c648b9e0083477bfcb649fe797662b78820
Author: rjoshi2 <re...@gmail.com>
Date:   2017-04-06T18:34:07Z

    Fix for potentially unclosed streams in ApexYarnLauncher

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] beam pull request #2454: [BEAM-1832] Fix for potentially unclosed streams in...

Posted by rekhajoshm <gi...@git.apache.org>.
Github user rekhajoshm closed the pull request at:

    https://github.com/apache/beam/pull/2454


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---