-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate python based visualization #4643
Comments
+1 |
What this implies is that, the TFDV/TFMA auto visualizations should be components in the golden tfx pipeline sample. |
I personally OK with it, especially considering current e2e experiences. |
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. |
/lifecycle frozen |
Blocker is to build a new way to visualize for tfx pipelines in #3970 |
Closing this issue. #3970 is closed. /close |
@rimolive: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Some problems we are facing with python based visualization (https://www.kubeflow.org/docs/pipelines/sdk/python-based-visualizations/):
Therefore, I'd want to deprecate python based visualization. I recommend fetching data via Kubeflow Pipelines SDK and visualizing from your own notebook instead, which gives you full control over your visualization process.
If you want some visualization to show for every run, you can run a component as part of your pipeline, the component should run the python visualization and expose HTML content of the visualization via https://www.kubeflow.org/docs/pipelines/sdk/output-viewer/#web-app.
The text was updated successfully, but these errors were encountered: