Closed maggiemhanna closed 4 years ago
This is because at compile time the parameter itself does not have a value. Do you think it's a legit use case to support treating item.a
as a string here @Ark-kun ?
PipelineParam
is a bit of an implementation detail. Users should treat it as opaque reference to some future data.param.value
was used to specify the default value of the pipeline parameter.Nevertheless, even semantically the value cannot exist at the pipeline compilation time, since the value is only created during the pipeline execution.
P.S. .set_display_name(str(item.a))
might actually work, although we are not supporting this.
Is there any other option to give a significant name to tasks in a loop?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.
Hello,
Extracting the string value of a PipelineParam (str(param.value)) always generates None.
I would like to extract the string value of a PipelineParam inside a pipeline so that I can use it to rename my component.
Example:
@dsl.pipeline(name='my-pipeline') def pipeline(loopidy_doop: dict = [{'a': "first", 'b': 2}, {'a': "second", 'b': 20}]):
Is there a way kubeflow can support this kind of operations?