-
Notifications
You must be signed in to change notification settings - Fork 998
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
Fix created timestamp related errors for BigQuery source #1474
Conversation
Signed-off-by: Jacob Klegar <[email protected]>
/kind housekeeping |
@@ -281,7 +296,12 @@ def test_historical_features_from_parquet_sources(): | |||
@pytest.mark.parametrize( | |||
"provider_type", ["local", "gcp"], | |||
) | |||
def test_historical_features_from_bigquery_sources(provider_type): | |||
@pytest.mark.parametrize( | |||
"created_timestamp_column", ["created", ""], |
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.
My only feedback is that these tests tend to run long, and will run even longer in the future the more we start to parameterize it. Would it be better to just have a single source (out of multiple) that doesnt have a created TS?
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.
Just one comment, otherwise it looks good
Signed-off-by: Jacob Klegar <[email protected]>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jklegar, 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 |
Signed-off-by: Jacob Klegar [email protected]
What this PR does / why we need it: Fix errors in historical retrieval when created_timestamp_column is not set on a BigQuery data source
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: