airbyte_databricks_cache
Databricks cache implementation for PyAirbyte
Installation
pip install airbyte # pre-requisite
pip install airbyte-databricks-cache
Usage
import airbyte as ab
import airbyte_databricks_cache # Must import to inject the module into airbyte.caches.databricks
from airbyte.caches.databricks import DatabricksCache # pylint: disable=E0401:import-error
# create airbyte source
source = ab.get_source(...)
# create DatabricksCache
cache_dbks = DatabricksCache(
access_token = ab.get_secret("databricks_access_token"),
server_hostname = ab.get_secret("databricks_server_hostname"),
http_path= ab.get_secret("databricks_http_path"),
catalog = ab.get_secret("databricks_catalog"),
schema_name = ab.get_secret("databricks_target_schema"),
staging_volume_w_location = ab.get_secret("databricks_staging_volume_w_location")
)
# read into cache
result = source.read(
cache=cache_dbks,
streams=['xxx'],
force_full_refresh=False,
write_strategy="append"
)
### OR
# write to destination
destination = ab.get_destination("destination-databricks", cache_dbks)
destination.write(source, ...)
Build and deploy
Happens via github workflow.
If building locally, manually:
poetry run python build.py
poetry build --format wheel
Run locally to test that import works:
poetry run python -c "import airbyte_databricks_cache"
Release mechanics:
# release
git fetch --tags origin
git describe --tags --abbrev=0
gh release create v0.1.8 --generate-notes
# gh release create v0.1.8 --target feat-workflow --generate-notes
git fetch --tags origin
# delete local tags if remote is deleted
git fetch origin --prune --prune-tags
## manual addons
# check long desc for pypi
twine check dist/*
Metadata
Release files for airbyte-databricks-cache 0.1.19
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| airbyte_databricks_cache-0.1.19-cp311-cp311-manylinux_2_35_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.35+ x86-64 | Details for airbyte_databricks_cache-0.1.19-cp311-cp311-manylinux_2_35_x86_64.whl |
| airbyte_databricks_cache-0.1.19-cp311-cp311-macosx_14_0_arm64.whl | CPython 3.11 | CPython 3.11 | macOS 14.0+ ARM64 | Details for airbyte_databricks_cache-0.1.19-cp311-cp311-macosx_14_0_arm64.whl |
Total release size: 977.9 kB
Release files / airbyte_databricks_cache-0.1.19-cp311-cp311-manylinux_2_35_x86_64.whl
| Download URL | airbyte_databricks_cache-0.1.19-cp311-cp311-manylinux_2_35_x86_64.whl |
|---|---|
| Size | 720.0 kB |
| Tags | CPython 3.11 Linux glibc 2.35+ x86-64 |
|
SHA-256 checksum How to use checksums |
98b992802a692f99a62a3c36fa7dfafd79851fd8504a9eb5211f3ef8f0a41b82
|
|
BLAKE2b-256 checksum How to use checksums |
c766f9533f052f5aaa5de11280883ebc42b0f98e45990a5806aa4ec2d182b5ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / airbyte_databricks_cache-0.1.19-cp311-cp311-macosx_14_0_arm64.whl
| Download URL | airbyte_databricks_cache-0.1.19-cp311-cp311-macosx_14_0_arm64.whl |
|---|---|
| Size | 257.9 kB |
| Tags | CPython 3.11 macOS 14.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
30934b96efd1f34ec61dd781df807acf175cdbc684825193dabd260cce087772
|
|
BLAKE2b-256 checksum How to use checksums |
c91e64c85e0015f34b0047e3d5286d888163ca21eb73ee1efa0b8c3870cbddc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for airbyte-databricks-cache 0.1.19
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.