You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Jay Sen (Jira)" <ji...@apache.org> on 2019/10/30 16:38:00 UTC

[jira] [Closed] (GOBBLIN-935) reloading job config throws NPE

     [ https://issues.apache.org/jira/browse/GOBBLIN-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Sen closed GOBBLIN-935.
---------------------------
    Resolution: Duplicate

> reloading job config throws NPE 
> --------------------------------
>
>                 Key: GOBBLIN-935
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-935
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-core
>    Affects Versions: 0.14.0
>            Reporter: Jay Sen
>            Assignee: Abhishek Tiwari
>            Priority: Major
>             Fix For: 0.15.0
>
>
> steps to reproduce
>  # run the gobblin in standalone ( i used standalone more but all other mode should be same)
>  # wait for any job to finish successfully or unsuccessfully.
>  # rename the completed job from <job_name>.pull.done to <job_name>.pull OR make any changes to the existing <job_name>.pull file ( like adding space )
>  # the job will be picked up by the observer and will throw NPE on {{SchedulerUtils}}.{{resolveTemplate}}
> This is due to the NULL JobSpecResolver. which happens only in case of the reloading of the job config and this does not happen in regular flow since it takes different code path.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)