Adding a dependent library to a Job task permanently adds it to the entire cluster?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2022 05:07 PM
Why does adding a dependent library to a Job task also permanently add it to the entire cluster?
I am using python wheels, and even when I remove the dependent library from a Job task, the wheel is still part of the cluster configuration.
If I then update the version of wheel used by the task, I then shows multiple versions of the wheel in the cluster libraries. I have no way to know which one is being used.
Labels:
- Labels:
-
Job Task
-
Python Wheel Task
-
Wheel