-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Submit scala jobs beta #8701
Submit scala jobs beta #8701
Conversation
…atest during release process
…labs#7409) (cherry picked from commit ada8860) Co-authored-by: Jeremy Cohen <jeremy@dbtlabs.com>
… (dbt-labs#7392) (cherry picked from commit 6fedfe0) Co-authored-by: Jeremy Cohen <jeremy@dbtlabs.com>
…t-labs#7376) (dbt-labs#7405) safe version attribute access in _check_resource_uniqueness
(cherry picked from commit 57e9096) Co-authored-by: Michelle Ark <MichelleArk@users.noreply.github.com>
…atest during release process
…est version has been modified (dbt-labs#7439) (dbt-labs#7460) (cherry picked from commit 2739d5f) Co-authored-by: Michelle Ark <MichelleArk@users.noreply.github.com>
…eRefResolver (dbt-labs#7438) (dbt-labs#7461) (cherry picked from commit 9874f9e) Co-authored-by: Michelle Ark <MichelleArk@users.noreply.github.com>
* Latest version should use un-suffixed alias * Latest version can be in un-suffixed file * FYI when unpinned ref to model with prerelease version * [WIP] Nicer error if versioned ref to unversioned model * Revert "Latest version should use un-suffixed alias" This reverts commit 3616c52. * Revert "[WIP] Nicer error if versioned ref to unversioned model" This reverts commit c9ae4af. * Define real event for UnpinnedRefNewVersionAvailable * Update pp test for implicit unsuffixed defined_in * Add changelog entry * Fix unit test * marky feedback * Add test case for UnpinnedRefNewVersionAvailable event (cherry picked from commit d53bb37) Co-authored-by: Jeremy Cohen <jeremy@dbtlabs.com>
…st during release process
…#7535) (dbt-labs#7548) * Back compat for previous retrurn type of 'collect_freshness' * Test fixups * PR feedback
(cherry picked from commit 19d6dab) Co-authored-by: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
…) (dbt-labs#7555) (cherry picked from commit 5a7b73b) Co-authored-by: Jeremy Cohen <jeremy@dbtlabs.com>
* Pin protobuf to >=4.0.0 * Changie (cherry picked from commit d34c511) Co-authored-by: Gerda Shank <gerda@dbtlabs.com>
…t-labs#7543) (dbt-labs#7557) (cherry picked from commit 40aca4b) Co-authored-by: Kshitij Aranke <kshitij.aranke@dbtlabs.com>
…atest during release process
dbt-labs#7605) * CT 2510 Throw error for duplicate versioned and non versioned model names (dbt-labs#7577) * Check for versioned/unversioned duplicates * Add new exception DuplicateVersionedUnversionedError * Changie * Handle packages when finding versioned and unversioned duplicates (cherry picked from commit 29f2cfc) * Issue AmbiguousAlias error after DuplicateResourceName
* Exclude some profile fields from Jinja rendering when they are not valid Jinja. (dbt-labs#7630) * CT-2583: Exclude some profile fields from Jinja rendering. * CT-2583: Add functional test. * CT-2583: Change approach to password jinja detection * CT-2583: Extract string constant and add additional checks * CT-2583: Improve unit test coverage * CT-2583: Update changelog entry to reflect new approach
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #8701 +/- ##
==========================================
- Coverage 86.65% 86.16% -0.49%
==========================================
Files 176 176
Lines 25674 25842 +168
==========================================
+ Hits 22247 22268 +21
- Misses 3427 3574 +147
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
hey @pekapa, first I applaud your ambition and tenacity to tackle this. We all would like to live in a world in which dbt becomes more language agnostic. I actually opened #5796 just over a year ago to start the conversation in that direction. @max-sixty has also done a lot of work considering how it might be done. More recently, I waxed poetic in our newsletter about linguistic relativism, which might also be up your alley. It's not the answer that you'd like to hear, but I don't think we can prioritize doing this in the short- or medium-term time frame. I'm going to close this PR now because we're not at the place to merge this for technical, architectural, and design decisions that would need to come first. That said, we do welcome your help in designing how we will support more data transformation APIs in dbt. To that end, I'd really appreciate:
|
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-spark PR: dbt-labs/dbt-spark/pull/891
Checklist