DQX_Installation #615
Unanswered
neerajborana
asked this question in
Q&A
Replies: 1 comment
-
|
Not really dependent on DQX. On Databricks the library wheel path must be an absolute workspace path. We have an example in the tool demo where we use wildcard, but we fetch the absolute path for installation: https://github.com/databrickslabs/dqx/blob/v0.9.3/demos/dqx_demo_tool.py#L151 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi DQX team,
According to the Databricks documentation, it appears that when specifying a wheel file from the workspace in job.yml (under the libraries section for a task), only the full path with the exact filename is supported, and wildcards like *.whl do not seem to work. However, some examples suggest wildcard usage might be allowed.
Could you please confirm:
Is it possible to use wildcards () in the wheel file path (e.g., /Workspace/Applications/dqx/wheels/databricks_labs_dqx-.whl) in job.yml?
If not supported, is there a recommended pattern to pick the latest or dynamically named wheel file?

Beta Was this translation helpful? Give feedback.
All reactions