Change Details

Alternative API for sensors, where a single sensor evaluation can launch multiple runs, each with unique run config and tags Expose a namedtuple class JobConfig that just contain tags and run_config, which could then be reused for partition set definitions, schedules, etc. Am open to renaming `JobConfig` (there seems to be some conflicts with k8s concepts?).

Alternative API for sensors, where a single sensor evaluation can launch multiple runs, each with unique run config and tags Expose a namedtuple class SensorTickData, that contains a list of SensorRunParams. SensorRunParams contain tags and run_config, which could then be reused for partition set definitions, schedules, etc.

Alternative API for sensors, where a single sensor evaluation can launch multiple runs, each with unique run config and tags Expose a namedtuple class JobConfig that just contain tags and run_configSensorTickData, which could then be reused for partition set definitions, schedulesthat contains a list of SensorRunParams. SensorRunParams contain tags and run_config, etc. Am open to renaming `JobConfig` (there seems to be some conflicts with k8s concepts?)which could then be reused for partition set definitions, schedules, etc.