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

feat: Support CartesianProductExec in comet #442

Closed
wants to merge 4 commits into from

Conversation

leoluan2009
Copy link
Contributor

@leoluan2009 leoluan2009 commented May 17, 2024

Which issue does this PR close?

Closes #199 .
TODO: need to support join condition after CrossJoin in Datafusion support join condition

Rationale for this change

What changes are included in this PR?

How are these changes tested?

@leoluan2009
Copy link
Contributor Author

@viirya help to start CI and review, thanks

@leoluan2009
Copy link
Contributor Author

@viirya thanks for your review, resolve your commets

Copy link
Contributor

@kazuyukitanimura kazuyukitanimura left a comment

Choose a reason for hiding this comment

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

LGTM (pending CI)

override def hashCode(): Int = Objects.hashCode(condition, left, right)

override lazy val metrics: Map[String, SQLMetric] =
CometMetricNode.baselineMetrics(sparkContext)
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you add more metrics here since Datafusion's cross join could emit additional metrics other than output rows?

@viirya
Copy link
Member

viirya commented May 28, 2024

@leoluan2009 You may need to generate plan stability results to pass the CI pipelines.

@@ -251,4 +251,18 @@ class CometJoinSuite extends CometTestBase {
}
}
}

// TODO: Add a test for CartesianProductExec with join filter after new DataFusion release
Copy link
Contributor

Choose a reason for hiding this comment

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

Add a github issue for the followup and refer to it here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fine

@leoluan2009
Copy link
Contributor Author

@leoluan2009 You may need to generate plan stability results to pass the CI pipelines.

OK, I will update soon, thanks!

@viirya
Copy link
Member

viirya commented Jun 12, 2024

@leoluan2009 Would you like to update the plan stability results? Thanks.

@leoluan2009
Copy link
Contributor Author

@leoluan2009 Would you like to update the plan stability results? Thanks.

Hi @viirya sorry for delay reply, I think this pr do not change the query plan for tpcds?

@viirya
Copy link
Member

viirya commented Jun 29, 2024

Hi @viirya sorry for delay reply, I think this pr do not change the query plan for tpcds?

Hmm, last time I saw the plans were changed so CI was failed, but now the CI doesn't fail on plan stability.

But CI currently failed on some other tests.

@leoluan2009 leoluan2009 closed this Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support CartesianProductExec
5 participants