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

Disable predicate pushdown optimizer #1400

Merged
merged 3 commits into from
Sep 10, 2024
Merged

Conversation

courtneyholcomb
Copy link
Contributor

Disable predicate pushdown optimizer. This has some bugs that we haven't investigated yet. It has been disabled in our servers, so it should be disabled in MetricFlow by default, too, to ensure where we're doing all our testing matches what's happening in production.

@cla-bot cla-bot bot added the cla:yes label Sep 6, 2024
@dbt-labs dbt-labs deleted a comment from github-actions bot Sep 6, 2024
@courtneyholcomb courtneyholcomb marked this pull request as ready for review September 6, 2024 22:39
@courtneyholcomb courtneyholcomb added the Run Tests With Other SQL Engines Runs the test suite against the SQL engines in our target environment label Sep 6, 2024
@github-actions github-actions bot removed the Run Tests With Other SQL Engines Runs the test suite against the SQL engines in our target environment label Sep 6, 2024
Copy link
Contributor

@tlento tlento left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

We need to regenerate the persistent schema for bigquery but I'm not sure if that's something that should happen lower down in this stack or on main or what. Please make sure that test passes before merging. Never mind it all works now.

@@ -29,6 +29,14 @@ def all_optimizations() -> FrozenSet[DataflowPlanOptimization]:
"""Convenience method for getting a set of all available optimizations."""
return frozenset((DataflowPlanOptimization.SOURCE_SCAN, DataflowPlanOptimization.PREDICATE_PUSHDOWN))

@staticmethod
def enabled_obtimizations() -> FrozenSet[DataflowPlanOptimization]:
Copy link
Contributor

Choose a reason for hiding this comment

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

nit:

Suggested change
def enabled_obtimizations() -> FrozenSet[DataflowPlanOptimization]:
def enabled_optimizations() -> FrozenSet[DataflowPlanOptimization]:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

whoops 😂

@tlento tlento added the Run Tests With Other SQL Engines Runs the test suite against the SQL engines in our target environment label Sep 9, 2024
@tlento tlento temporarily deployed to DW_INTEGRATION_TESTS September 9, 2024 06:11 — with GitHub Actions Inactive
@tlento tlento temporarily deployed to DW_INTEGRATION_TESTS September 9, 2024 06:11 — with GitHub Actions Inactive
@tlento tlento temporarily deployed to DW_INTEGRATION_TESTS September 9, 2024 06:11 — with GitHub Actions Inactive
@tlento tlento temporarily deployed to DW_INTEGRATION_TESTS September 9, 2024 06:11 — with GitHub Actions Inactive
@github-actions github-actions bot removed the Run Tests With Other SQL Engines Runs the test suite against the SQL engines in our target environment label Sep 9, 2024
Base automatically changed from court/custom-grain-dfp-2 to main September 10, 2024 15:57
@courtneyholcomb courtneyholcomb added the Run Tests With Other SQL Engines Runs the test suite against the SQL engines in our target environment label Sep 10, 2024
@github-actions github-actions bot removed the Run Tests With Other SQL Engines Runs the test suite against the SQL engines in our target environment label Sep 10, 2024
@courtneyholcomb courtneyholcomb merged commit 024ca33 into main Sep 10, 2024
29 checks passed
@courtneyholcomb courtneyholcomb deleted the court/custom-grain-dfp-3 branch September 10, 2024 18:37
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.

2 participants