- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2022 04:12 PM
Can someone provide me an example for a python_wheel_task and what the entry_point field should be?
The jobs UI help popup says this about "entry_point":
"Function to call when starting the wheel, for example: main. If the entry point does not exist in the meta-data of the wheel distribution, the function will be called directly using `$packageName.$entryPoint()`."
However, an entry point in python is a combination of the group and a name. e.g. in my setup.py
entry_points = {
'my_jobs': [
'a_job = module_name:job_function'
]
},Here the group is "my_jobs" and the name is "a_job". For databricks, should I make entry_point `a_job`, `my_jobs.a_job`, or does databricks require a specific group name for wheels that are run as tasks?
I couldn't find any documentation online to clarify this.
- Labels:
-
Entry Point
-
Python Wheel Task
-
Wheel