Feature request: support placeholders in the data parameter of TrainingStep constructor #97
Comments
shivlaks
pushed a commit
that referenced
this issue
Jun 19, 2021
…n for InputDataConfig and OutputDataConfig (#142) Currently, it is not possible to specify the output path to TrainingStep. It needs to be defined at the Estimator level, which does not support placeholders. This change will make it possible to insert a placeholder output path from the TrainingStep definition and propagate it dynamically to the Estimator. This change change also makes the TrainingStep data parameter compatible with placeholders. There are other feature requests to make other TrainingStep arguments and ProcessingStep arguments compatible with placeholders. They will be addressed in a separate PR where the implementation could maybe be done at a higher level to avoid repetition. Closes #98 #97 #80
|
Implemented in #142 which has now been merged 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the
dataparameter to theTrainingStepconstructor does not support placeholders, requiring the s3 location of the dataset to be known at workflow creation time.It would be useful for this parameter to accept dynamic s3 uri, via placeholders.
The text was updated successfully, but these errors were encountered: