dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
dbt is the T in ELT. Organize, cleanse, denormalize, filter, rename, and pre-aggregate the raw data in your warehouse so that it's ready for analysis.
dbt-spark
The dbt-ocean-spark package contains all of the code enabling dbt to work with Apache Spark on Ocean. For
more information, consult the docs.
Getting started
- Install dbt
- Read the introduction and viewpoint
Running locally
A docker-compose environment starts a Spark Thrift server and a Postgres database as a Hive Metastore backend.
Note: dbt-spark now supports Spark 3.1.1 (formerly on Spark 2.x).
The following command would start two docker containers
docker-compose up -d
It will take a bit of time for the instance to start, you can check the logs of the two containers. If the instance doesn't start correctly, try the complete reset command listed below and then try start again.
Create a profile like this one:
spark_testing:
target: local
outputs:
local:
type: ocean_spark
method: http
host: api.spotinst.io
port: 443
cluster: osc-[clusterId]
account: acc-[accountId]
app: spark-hive-[appId]
schema: analytics
connect_retries: 5
connect_timeout: 60
retry_all: true
Connecting to the local spark instance:
- The Spark UI should be available at http://console.spotinst.com/ocean/spark/cluster/{clusterId}/app/{appId}/sparkUI/jobs
- The endpoint for SQL-based testing is at
http://localhost:10000and can be referenced with the Hive or Spark JDBC drivers using connection stringjdbc:hive2://localhost:10000and default credentialsdbt:dbt
Note that the Hive metastore data is persisted under ./.hive-metastore/, and the Spark-produced data under ./.spark-warehouse/. To completely reset you environment run the following:
docker-compose down
rm -rf ./.hive-metastore/
rm -rf ./.spark-warehouse/
Reporting bugs and contributing code
Code of Conduct
Everyone interacting in the dbt project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the PyPA Code of Conduct.
Join the dbt Community
- Be part of the conversation in the dbt Community Slack
- Read more on the dbt Community Discourse
Reporting bugs and contributing code
- Want to report a bug or request a feature? Let us know on Slack, or open an issue
- Want to help us build dbt? Check out the Contributing Guide
Code of Conduct
Everyone interacting in the dbt project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the dbt Code of Conduct.
Metadata
Release files for dbt-ocean-spark 1.6.2
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 |
|---|---|---|---|---|
| dbt_ocean_spark-1.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / dbt_ocean_spark-1.6.2-py3-none-any.whl
| Download URL | dbt_ocean_spark-1.6.2-py3-none-any.whl |
|---|---|
| Size | 45.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2cadab32c24c3230dddd6c82080b6c6b0aecc974306c30d48bf7140b7ce74194
|
|
BLAKE2b-256 checksum How to use checksums |
c842e28112168ecee8a6a2c1c8bf243f66f83faa30d142047842d885851293ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for dbt-ocean-spark 1.6.2
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.