Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
New TFX IR MLMD does not store pipeline_name property in pipeline_run context
See original GitHub issueWe have internal code that relies on using Context properties in MLMD for retrieving all runs related to a pipeline. Seems new TFX IR does not store property to retrieve pipeline name from pipeline_run context.
Related internal code: #2415 PipelineContext -> _get_runs
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10 (7 by maintainers)
Top Results From Across the Web
ML Metadata | TFX - TensorFlow
This graphic shows a high-level overview of the various components that are part of MLMD. ML Metadata Overview. Metadata storage backends and ...
Read more >tfx Changelog - pyup.io
Artifact/Channel properties now support the new MLMD PROTO property type. ... Calling `TfxRunner.run(pipeline)` with the Pipeline IR proto will no longer
Read more >Explain TFX Metadata Store data model definitions
Is there a specific portion that you are having an issue understanding or is it more general? If it is more general, there...
Read more >Integrations - ZenML API Reference
The Airflow integration sub-module powers an alternative to the local orchestrator. You can enable it by registering the Airflow orchestrator with the CLI...
Read more >Source - GitHub
... **sdk:** Fix "No KFP components found in file" error. ... BREAKING CHANGES * **sdk:** Support submitting pipeline IR in yaml format via...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FWIW, the context returned from the above code by(@ymyfish) is ‘pipeline_contexts’ not ‘pipeline_run_contexts’. I think that the idea from @casassg is the valid approach if pipeline runs are needed.
This could be addressed by using the new ParentContext feature in MLMD 1.X (aka Pipeline is a ParentContext for PipelineRun context)