cylondata/twister2

refactoring Config and JobConfig

Opened this issue · 1 comments

pulasthi commented

Currently the users see both the Config and JobConfig objects, which can be confusing.

  1. JobConfig: This can be renamed to JobParameters. It can hold job specific parameters supplied by the user. It will we part of Job object. It will be provided to each Worker with IWorker interface.
  2. Config: This will have parameters that are specific to Twister2 system. Users should neither see this Config object when they submit the job, nor in IWorker.

A possible solution would be to hide Config from users. When they submit the job, they don't see Config

chathurawidanage commented

edu.iu.dsc.tws.rsched.job.Twister2Submitter#submitJob(edu.iu.dsc.tws.api.Twister2Job) added from 0.4.0