[jira] [Commented] (NIFI-4978) Stopping of ReportLineageToAtlas can cause NPE

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

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

ASF GitHub Bot commented on NIFI-4978:
--------------------------------------

GitHub user ijokarumawak opened a pull request:

    https://github.com/apache/nifi/pull/2548

    NIFI-4978: Fixed ReportLineageToAtlas NPE when unscheduled

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


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

    $ git pull https://github.com/ijokarumawak/nifi nifi-4978

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

    https://github.com/apache/nifi/pull/2548.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 #2548
    
----
commit 31bfbc1f8a39d45884f599adb4de33899ff31e67
Author: Koji Kawamura <ij...@...>
Date:   2018-03-14T19:22:26Z

    NIFI-4978: Fixed ReportLineageToAtlas NPE when unscheduled

----


> Stopping of ReportLineageToAtlas can cause NPE
> ----------------------------------------------
>
>                 Key: NIFI-4978
>                 URL: https://issues.apache.org/jira/browse/NIFI-4978
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.5.0
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>            Priority: Minor
>
> Stopping ReportLineageToAtlas can cause following NPE.
> {code}
> 2018-02-21 11:34:16,490 INFO [Timer-Driven Process Thread-8] org.apache.atlas.AtlasBaseClient Client has only one service URL, will use that for all actions: http://ctr-e138-1518143905142-29976-01-000002.hwx.site:21000
> 2018-02-21 11:34:16,711 INFO [StandardProcessScheduler Thread-4] o.a.n.c.s.TimerDrivenSchedulingAgent Stopped scheduling ReportLineageToAtlas[id=b7bf3781-0161-1000-ffff-ffffafd9ddbd] to run
> 2018-02-21 11:34:16,760 INFO [Flow Service Tasks Thread-2] o.a.nifi.controller.StandardFlowService Saved flow controller org.apache.nifi.controller.FlowController@2a3e0c4a // Another save pending = false
> 2018-02-21 11:34:17,110 ERROR [Timer-Driven Process Thread-8] o.a.n.a.reporting.ReportLineageToAtlas ReportLineageToAtlas[id=b7bf3781-0161-1000-ffff-ffffafd9ddbd] Error running task ReportLineageToAtlas[id=b7bf3781-0161-1000-ffff-ffffafd9ddbd] due to java.lang.NullPointerException
> 2018-02-21 11:34:17,111 ERROR [Timer-Driven Process Thread-8] o.a.n.a.reporting.ReportLineageToAtlas ReportLineageToAtlas[id=b7bf3781-0161-1000-ffff-ffffafd9ddbd] : java.lang.NullPointerException
> java.lang.NullPointerException: null
>         at org.apache.nifi.atlas.reporting.ReportLineageToAtlas.onTrigger(ReportLineageToAtlas.java:614)
>         at org.apache.nifi.controller.tasks.ReportingTaskWrapper.run(ReportingTaskWrapper.java:41)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecu
> {code}
> This issue was reported by [~nayakmahesh616]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)