You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

  • Motivation:
    • current way of managing job config via files makes it hard to manage job configurations, persisting it in MySQL would make it easier to manage and also provide various CRUD API interfaces to mange the job configuration.
  • Proposed Change: 
    • create MySQL table `gobblin_job_config`
    • create REST endpoints for CRUD operations
    • add functionality to detect change in any job config and schedule or trigger job accordingly ( similar to current mechanism based on file change )
  • New or Changed Public Interfaces:
    • /create_job
    • /modify_job
    • /delete_job
  • Migration Plan and Compatibility: 
    • since this is new functionality, in addition to the current file based job config, user can select either one to manage the job.
  • Rejected Alternatives:
    • use JDBI ?
    • use REST.li ?

Design:


MySQL table:

gobblin_job_config
CREATE TABLE `gobblin_job_store` (
  `job_id` varchar(255) NOT NULL,
  `job_name` varchar(255) NOT NULL,
  `job_config` json DEFAULT NULL,
  `created_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `modified_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`job_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;



  • No labels