-
Notifications
You must be signed in to change notification settings - Fork 161
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
Dataproc config for serverless in profile and fix quoting #578
Dataproc config for serverless in profile and fix quoting #578
Conversation
This adds a `dataproc_batch` key for specifying the Dataproc Batch configuration. At runtime this is used to populate the google.cloud.dataproc_v1.types.Batch object before it is submitted to the Dataproc service. To avoid having to add explicit support for every option offered by the service, and having to chase after a moving target as Google's API evolves, this key accepts arbitrary yaml, which is mapped to the Batch object on a best effort basis. Signed-off-by: Torkjel Hongve <th@kinver.io>
- Make dataproc_batch key optional. - Unit tests - Move configuration of the `google.cloud.dataproc_v1.Batch` object to a separate function. Signed-off-by: Torkjel Hongve <th@kinver.io>
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-bigquery contributing guide. |
…p python_submissions.py
dev-requirements.txt
Outdated
@@ -1,7 +1,7 @@ | |||
# install latest changes in dbt-core | |||
# TODO: how to automate switching from develop to version branches? | |||
git+https://github.com/dbt-labs/dbt-core.git#egg=dbt-core&subdirectory=core | |||
git+https://github.com/dbt-labs/dbt-core.git#egg=dbt-tests-adapter&subdirectory=tests/adapter | |||
git+https://github.com/dbt-labs/dbt-core.git@addPyRelationNameMacro#egg=dbt-core&subdirectory=core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: dbt-core pointer once approved
@@ -184,6 +221,25 @@ def test_acquire_connection_oauth_validations(self, mock_open_connection): | |||
connection.handle | |||
mock_open_connection.assert_called_once() | |||
|
|||
@patch('dbt.adapters.bigquery.connections.get_bigquery_defaults', return_value=('credentials', 'project_id')) | |||
@patch('dbt.adapters.bigquery.BigQueryConnectionManager.open', return_value=_bq_conn()) | |||
def test_acquire_connection_dataproc_serverless(self, mock_open_connection, mock_get_bigquery_defaults): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: does this go beyond flake8 and black line length?
@cla-bot check |
1 similar comment
@cla-bot check |
The cla-bot has been summoned, and re-checked this pull request! |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.4.latest 1.4.latest
# Navigate to the new working tree
cd .worktrees/backport-1.4.latest
# Create a new branch
git switch --create backport-578-to-1.4.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f2f0e4272c42b2c2b59847279373c36fb08e3e37
# Push it to GitHub
git push --set-upstream origin backport-578-to-1.4.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.4.latest Then, create a pull request where the |
#3661) Resolves #3382 ## What are you changing in this pull request and why? The dataproc_batch config field for configuring Python models running on GCP Dataproc Serverless was added in [dbt-labs/dbt-bigquery#578](dbt-labs/dbt-bigquery#578), but it isn't documented yet. This PR adds the missing documentation for this field. ## Checklist - [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines. - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
resolves #350
Description
Checklist
changie new
to create a changelog entry