clickhouse-java
dbt-unit-testing
clickhouse-java | dbt-unit-testing | |
---|---|---|
1 | 7 | |
1,370 | 404 | |
0.7% | 1.5% | |
9.0 | 7.7 | |
4 days ago | 14 days ago | |
Java | Shell | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clickhouse-java
-
SQL should be your default choice for data engineering pipelines
Agree with the OP that SQL will almost assuredly still be in use for 20+ years in the future, given the simplicity and flexibility of the declarative language, standardization, and as applicable to today as it was then to our big data problems.
Any discussion of SQL at scale must include ClickHouse [https://clickhouse.com/docs/en/install#self-managed-install], given it's broad open-source use, integrations available for Spark with JDBC [https://github.com/ClickHouse/clickhouse-jdbc/] or the open-source Spark-ClickHouse Connector [https://github.com/housepower/spark-clickhouse-connector], and capability to scale SQL as a network service.
Disclosure: I work for ClickHouse
dbt-unit-testing
-
The SQL Unit Testing Landscape: 2023
If you use dbt for transformations Dbt Unit Testing (https://github.com/EqualExperts/dbt-unit-testing) is getting some attention (https://www.thoughtworks.com/radar/languages-and-frameworks?blipid=202304042)
-
Data-eng related highlights from the latest Thoughtworks Tech Radar
dbt-unit-testing
- I'm not getting it...what's the point of DBT?
-
Ask HN: How do you test SQL?
We use this and take an example-based tests approach for any non-trivial tables: https://github.com/EqualExperts/dbt-unit-testing
-
SQL should be your default choice for data engineering pipelines
> How do you test some SQL logic in isolation?
I do this using sql
1. Extracting an 'ephemeral model' to different model file
2. Mock out this model in upstream model in unit tests https://github.com/EqualExperts/dbt-unit-testing
3. Write unit tests for this model.
This is not different than regular software development in a language like java.
I would argue its even better better because unit tests are always in tabular format and pretty easy to understand. Java unit tests on other hand are never read by devs in practice.
-
Unit testing with dbt
I haven't done it yet but there are some popular blogs as well as a DBT package someone created.
-
Modern Data Modeling: Start with the End?
> I really don’t understand the communities obsession with unwieldy tools like DBT.
It lets me write test first sql transforms. I never thought TDD sql would be possible. My sql is so much more readable with common logic extracted into ephmeral models. I practice same method to write clear code to write sql, eg: too many mocks = refactor into separate model ( class) .
I think DBT made this possible with refs that can be swapped out with mocks. This is the awesome library I am using https://github.com/EqualExperts/dbt-unit-testing
What are some alternatives?
jaybird - JDBC driver for Firebird
sqlglot - Python SQL Parser and Transpiler
data-diff - Compare tables within or across databases
dbt-expectations - Port(ish) of Great Expectations to dbt test macros
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
SS-Unit - A 100% T-SQL based unit testing framework for SQL Server
hash-db - Experimental distributed pseudomultimodel keyvalue database (it uses python dictionaries) imitating dynamodb querying with join only SQL support, distributed joins and simple Cypher graph support and document storage
spark-style-guide - Spark style guide
pg-mem - An in memory postgres DB instance for your unit tests
bytebase - The GitLab/GitHub for database DevOps. World's most advanced database DevOps and CI/CD for Developer, DBA and Platform Engineering teams.
fugue - A unified interface for distributed computing. Fugue executes SQL, Python, Pandas, and Polars code on Spark, Dask and Ray without any rewrites.
integresql - IntegreSQL manages isolated PostgreSQL databases for your integration tests.