Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scalable mono repo data engineering workloads #44

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dantaylrr
Copy link

This is an "in-depth" example of a scalable, modularised repo structure for all Data Engineering workloads using DABs. It supports the following:

  • All types of artefacts (python scripts, notebooks, DLT pipelines & libraries).
  • Jobs (both serverless & classic).
  • Environment / dependancy overrides for serverless jobs.
  • Pipelines.

The aim of this example is not to define a de-facto approach for DABs projects but to give companies / individuals an example as to how they might structure all of their Databricks application code in a single mono-repo.

All additional fixtures such as Makefiles, workflows, pre-commit hooks, etc. are entirely optional & can be removed if needed.

All in-line comments & README instructions can be altered so please let me know if anything has been missed / is too specific / doesn't make sense.

@@ -0,0 +1,79 @@
# This is a Databricks asset bundle definition for my_project.
# See https://docs.databricks.com/dev-tools/bundles/index.html for documentation.
bundle:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding databricks_cli_version can help mitigate issues related to the CLI version. Since new features are frequently added, this can be helpful.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ref: #19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants