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

Bring back dataset as a required field for BigQuery profile #1033

Merged
merged 1 commit into from
Jun 7, 2024

Conversation

pankajkoti
Copy link
Contributor

In PR #1017, we attempted to remove dataset from the required fields list for the BigQuery profile. However, we realised that this is failing BiqQuery dbt operations as it indeed is a required field. Hence, bring back the same as a required field. This is also necessary for building the mock profile where we construct the profile by taking in consideration only the required fields.

closes: #1031

In PR #1017, we attempted to remove `dataset` from the required
fields list for the BigQuery profile. However, we realised that
this is failing BiqQuery dbt operations as it indeed is a required
field. Hence, bring back the same as a required field. This is
also necessary for building the mock profile where we construct
the profile by taking in consideration only the required fields.

closes: #1031
Copy link

netlify bot commented Jun 7, 2024

Deploy Preview for sunny-pastelito-5ecb04 canceled.

Name Link
🔨 Latest commit 284db94
🔍 Latest deploy log https://app.netlify.com/sites/sunny-pastelito-5ecb04/deploys/6662f5f8e9967e0008fa36f4

@pankajkoti pankajkoti requested a review from tatiana June 7, 2024 12:21
Copy link

codecov bot commented Jun 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.77%. Comparing base (3a63bee) to head (284db94).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1033   +/-   ##
=======================================
  Coverage   95.77%   95.77%           
=======================================
  Files          62       62           
  Lines        2979     2979           
=======================================
  Hits         2853     2853           
  Misses        126      126           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pankajkoti pankajkoti marked this pull request as ready for review June 7, 2024 12:36
@dosubot dosubot bot added size:XS This PR changes 0-9 lines, ignoring generated files. area:profile Related to ProfileConfig, like Athena, BigQuery, Clickhouse, Spark, Trino, etc profile:bigquery Related to BigQuery ProfileConfig labels Jun 7, 2024
Copy link
Collaborator

@tatiana tatiana left a comment

Choose a reason for hiding this comment

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

@pankajkoti this looks great, thanks a lot for the very fast fix!

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jun 7, 2024
@tatiana tatiana merged commit 803776a into main Jun 7, 2024
64 checks passed
@tatiana tatiana deleted the bq-make-dataset-required-field branch June 7, 2024 12:40
pankajkoti added a commit that referenced this pull request Jun 7, 2024
In PR #1017, we attempted to remove `dataset` from the required fields
list for the BigQuery profile. However, we realised that this is failing
BiqQuery dbt operations as it indeed is a required field. Hence, bring
back the same as a required field. This is also necessary for building
the mock profile where we construct the profile by taking in
consideration only the required fields.

Closes: #1031
(cherry picked from commit 803776a)
@pankajkoti pankajkoti mentioned this pull request Jun 7, 2024
pankajkoti added a commit that referenced this pull request Jun 7, 2024
Bug fixes

* Bring back ``dataset`` as a required field for BigQuery profile by
@pankajkoti in #1033

Enhancements

* Only run ``dbt deps`` when there are dependencies by @tatiana in #1030

Docs

* Fix docs so it does not reference non-existing ``get_dbt_dataset`` by
@tatiana in #1034

---------

Co-authored-by: Tatiana Al-Chueyr <[email protected]>
arojasb3 pushed a commit to arojasb3/astronomer-cosmos that referenced this pull request Jul 14, 2024
…omer#1033)

In PR astronomer#1017, we attempted to remove `dataset` from the required fields
list for the BigQuery profile. However, we realised that this is failing
BiqQuery dbt operations as it indeed is a required field. Hence, bring
back the same as a required field. This is also necessary for building
the mock profile where we construct the profile by taking in
consideration only the required fields.

Closes: astronomer#1031
arojasb3 pushed a commit to arojasb3/astronomer-cosmos that referenced this pull request Jul 14, 2024
Bug fixes

* Bring back ``dataset`` as a required field for BigQuery profile by
@pankajkoti in astronomer#1033

Enhancements

* Only run ``dbt deps`` when there are dependencies by @tatiana in astronomer#1030

Docs

* Fix docs so it does not reference non-existing ``get_dbt_dataset`` by
@tatiana in astronomer#1034

---------

Co-authored-by: Tatiana Al-Chueyr <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:profile Related to ProfileConfig, like Athena, BigQuery, Clickhouse, Spark, Trino, etc lgtm This PR has been approved by a maintainer profile:bigquery Related to BigQuery ProfileConfig size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: BigQuery profile target 'dev' invalid: 'schema' is a required property
2 participants