DM-16822: Use pipe.base.*DatasetConfig in MetricTask configs #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modifies the Gen 2 class
compatibility.MetricTask
to useInputDatasetConfig
to specify its inputs. This change will simplify the transition to the Gen 3MetricTask
, once it exists. I'm not sure if the documentation makes it clear enough thatInputDatasetConfig
is the primary way forMetricTask
to describe its inputs.While the original ticket also asked to use
OutputDatasetConfig
, this can't be done until Butler support forMeasurement
is available.