[jira] [Commented] (APEXMALHAR-2342) Fix null pointer exception in AbstractFileOutputOperator setup

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on APEXMALHAR-2342:
--------------------------------------------

GitHub user darinnee opened a pull request:

    https://github.com/apache/apex-malhar/pull/496

    APEXMALHAR-2342 Check file exists to prevent null pointer exception …

    …in AbstractFileOutputOperator recovery setup

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

    $ git pull https://github.com/darinnee/apex-malhar APEXMALHAR-2342

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

    https://github.com/apache/apex-malhar/pull/496.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 #496
    
----
commit 1df0b523ad522595f6bb30ff76aacb57d239807f
Author: Darin Nee <da...@gmail.com>
Date:   2016-11-15T17:57:07Z

    APEXMALHAR-2342: check file exists to prevent null pointer exception in AbstractFileOutputOperator recovery setup

----


> Fix null pointer exception in AbstractFileOutputOperator setup
> --------------------------------------------------------------
>
>                 Key: APEXMALHAR-2342
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2342
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>    Affects Versions: 3.5.0
>            Reporter: Darin Nee
>
> After finalizing a rolling output file, if AbstractFileOutputOperator container subsequently fails before the next checkpoint, it encounters a null pointer exception in the setup method when the operator is relaunched, and the container endlessly cycles.



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