You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gobblin.apache.org by "Sudarshan Vasudevan (JIRA)" <ji...@apache.org> on 2019/06/04 18:48:00 UTC

[jira] [Updated] (GOBBLIN-795) Make JobCatalog optional for FsJobConfigurationManager

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

Sudarshan Vasudevan updated GOBBLIN-795:
----------------------------------------
    Summary: Make JobCatalog optional for FsJobConfigurationManager  (was: Make jobCatalog optional for FsJobConfigurationManager)

> Make JobCatalog optional for FsJobConfigurationManager
> ------------------------------------------------------
>
>                 Key: GOBBLIN-795
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-795
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-cluster
>    Affects Versions: 0.15.0
>            Reporter: Sudarshan Vasudevan
>            Assignee: Hung Tran
>            Priority: Major
>             Fix For: 0.15.0
>
>
> Existing behavior enforces the need to provide a JobCatalog. We relax this requirement and allow the JobConfigurationManager to bootstrap the gobblin cluster with job configs from a configured location (as opposed to bootstrapping from a JobCatalog). 



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