dbxcarta-submit
Operator tooling for building, uploading, and submitting
dbxcarta Databricks jobs. It wraps
databricks-job-runner and
knows how to stage a neocarta
connector wheel onto a Unity Catalog Volume and submit its ingest job.
The distribution installs:
- the
dbxcartaconsole command (the operator CLI), and - the
dbxcarta.submitimport path, including thesubmit_neocarta_ingestlibrary function.
Install
pip install dbxcarta-submit
The wheel is self-contained: its only external dependency is
databricks-job-runner. The dbxcarta.core modules it uses are bundled into
the wheel, so no separate install is required.
Library use
from pathlib import Path
from dbxcarta.submit import submit_neocarta_ingest
# Stage a prebuilt neocarta connector wheel and submit the ingest job.
# The catalog, Volume, profile, and Neo4j secrets come from the selected
# dbxcarta overlay (DBXCARTA_ENV_FILE or --env-file), exactly as the CLI
# resolves them.
submit_neocarta_ingest(Path("dist/neocarta-1.0.0-py3-none-any.whl"))
The ingest job uses the Neo4j Spark Connector, a JVM cluster library, so it must
run on classic (non-serverless) compute. submit_neocarta_ingest defaults to
compute_mode="cluster".
CLI use
dbxcarta --help
See the dbxcarta repository for the operator workflow.
Metadata
Release files for dbxcarta-submit 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dbxcarta_submit-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / dbxcarta_submit-1.4.0-py3-none-any.whl
| Download URL | dbxcarta_submit-1.4.0-py3-none-any.whl |
|---|---|
| Size | 33.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3442283c483f693f8efd38418f8783003dec6cbef707f396b63a1650d29311ac
|
|
BLAKE2b-256 checksum How to use checksums |
46ecea071be5611fdf7691132beaebcb6003770f24fc65658f2770fc1ce95d8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 14, 2026.
Transparency log