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

Add location to BigQueryOfflineStoreConfig #1921

Merged
merged 2 commits into from
Oct 3, 2021

Conversation

loftiskg
Copy link
Contributor

@loftiskg loftiskg commented Oct 2, 2021

What this PR does / why we need it:

Currently, the BigQueryOfflineStore default to the 'us' GCP region and does provide a configuration to change the region. This PR adds a config to BigQueryOfflineStoreConfig that allows defining a GCP region for a BigQueryOfflineStore.

The default behavior (defaulting to region 'us') is maintained (ie. no location/region specified in the offline store configuration).

Which issue(s) this PR fixes:

Fixes #1728

Does this PR introduce a user-facing change?:

Add location configuration to BigQueryOfflineStore

Signed-off-by: Kevin Loftis <loftiskg@gmail.com>
@feast-ci-bot
Copy link
Collaborator

Hi @loftiskg. Thanks for your PR.

I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@codecov-commenter
Copy link

codecov-commenter commented Oct 2, 2021

Codecov Report

Merging #1921 (55fd2a1) into master (f31ea81) will increase coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1921      +/-   ##
==========================================
+ Coverage   82.97%   82.98%   +0.01%     
==========================================
  Files          96       96              
  Lines        7376     7377       +1     
==========================================
+ Hits         6120     6122       +2     
+ Misses       1256     1255       -1     
Flag Coverage Δ
integrationtests 74.42% <100.00%> (+0.01%) ⬆️
unittests 60.64% <50.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
sdk/python/feast/infra/offline_stores/bigquery.py 80.11% <100.00%> (+0.11%) ⬆️
sdk/python/feast/infra/utils/aws_utils.py 83.92% <0.00%> (+0.89%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f31ea81...55fd2a1. Read the comment docs.

@@ -52,6 +52,9 @@ class BigQueryOfflineStoreConfig(FeastConfigBaseModel):
project_id: Optional[StrictStr] = None
""" (optional) GCP project name used for the BigQuery offline store """

location: Optional[StrictStr] = None
""" (optional) GCP location name used for the BigQuery offline store """
Copy link
Member

Choose a reason for hiding this comment

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

I think it would be really useful to provide an example as part of this comment, like US or EU

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good call. Added some additional documentation.

@woop
Copy link
Member

woop commented Oct 2, 2021

Thanks for this PR @loftiskg!

@woop woop added the kind/feature New feature or request label Oct 2, 2021
@woop
Copy link
Member

woop commented Oct 2, 2021

Just left a small nitpick comment on the config comment, but otherwise it's good to merge.

Signed-off-by: Kevin Loftis <loftiskg@gmail.com>
@feast-ci-bot feast-ci-bot removed the lgtm label Oct 2, 2021
@feast-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: loftiskg, woop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@woop
Copy link
Member

woop commented Oct 2, 2021

/lgtm

@feast-ci-bot feast-ci-bot merged commit 982b7cd into feast-dev:master Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for BQ Datasets not in US
4 participants