This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Submit scala jobs beta #891
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Github Build Bot <[email protected]>
…on on refresh (dbt-labs#724) (dbt-labs#727) * update `drop_relation()` to drop `target_relation` instead of `old_relation`; these should be the same anyway, but `old_relation` doesn't always get populated * add in old relation type in cases where the relation type changes (cherry picked from commit 44b10f9) Co-authored-by: Mike Alfare <[email protected]>
Co-authored-by: Github Build Bot <[email protected]>
* CT-2223: Add CONSTRAINT_SUPPORT mapping to adapter implementation * CT-2223: Model constraints implemented for spark * CT-2223: Add unit test * CT-2223: Exclude test not applicable to spark * CT-2223: Another unit test fix. * CT-2223: Final (?) unit test fix * CT-2223: Final (??) unit test fix * Update .changes/unreleased/Features-20230427-123135.yaml Co-authored-by: Doug Beatty <[email protected]> --------- Co-authored-by: Doug Beatty <[email protected]> (cherry picked from commit 4f1039d) Co-authored-by: Peter Webb <[email protected]>
Co-authored-by: Github Build Bot <[email protected]>
Co-authored-by: Github Build Bot <[email protected]>
# Conflicts: # .bumpversion.cfg # CHANGELOG.md # dbt/adapters/spark/__version__.py # dbt/adapters/spark/impl.py # setup.py # tests/functional/adapter/test_constraints.py
5 tasks
pekapa
changed the title
Contributor
|
This PR has been marked as Stale because it has been open with no activity as of late. If you would like the PR to remain open, please comment on the PR or else it will be closed in 7 days. |
Contributor
|
Although we are closing this PR as stale, it can still be reopened to continue development. Just add a comment to notify the maintainers. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Starting on version 1.3 DBT Python models became available. Another very common programming language for submitting spark jobs is Scala. This PR enables Scala models to be built with DBT
Solution
Using the structure created by Python models we can extend it to also support Scala models.
The parser for Scala is not widely available so a "cheap" version was built to provide just the minimum needed for it. More complex solutions (using ANTLR, for example) might be desired in the future.
Since the Python validator is missing tests we are also skipping those for now here. Same for typed annotations, it follows the precedent set by the Python models code.
Related dbt-core PR: dbt-labs/dbt-core/pull/8701
Checklist