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

[BEAM-5817] Add Nexmark SqlBoundedSideInputJoin #7114

Merged
merged 4 commits into from Nov 24, 2018

Conversation

kennknowles
Copy link
Member

This adds a SQL variant of the bounded side input join query to the Nexmark suite. It is in the global window. It is up to the SQL optimizer to always find a side input join plan, since otherwise this pipeline needs windowing added in order to work.


Follow this checklist to help us incorporate your contribution quickly and easily:

  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- --- --- --- ---
Java Build Status Build Status Build Status Build Status Build Status Build Status Build Status Build Status
Python Build Status --- Build Status
Build Status
Build Status --- --- ---

@kennknowles
Copy link
Member Author

R: @akedin @apilloud @xumingmin

Minor tweaks to BeamJoinRel and then it "just works" which is cool!

@@ -198,6 +195,9 @@ private boolean isSideInputJoin() {
if ((leftRows.isBounded() == PCollection.IsBounded.BOUNDED
&& rightRows.isBounded() == PCollection.IsBounded.BOUNDED)
|| (leftRows.isBounded() == UNBOUNDED && rightRows.isBounded() == UNBOUNDED)) {
verifySupportedTrigger(leftRows);
Copy link
Member Author

Choose a reason for hiding this comment

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

@akedin I think you added this - can you double check my thinking that it is safe to move into here?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think so, this is the CoGBK path where we care about the windowing+triggering. The other path is side-input where it should work anyhow, I think

@@ -76,6 +76,6 @@ public BoundedSideInputJoinModel(NexmarkConfiguration configuration) {

@Override
protected Collection<String> toCollection(Iterator<TimestampedValue<Bid>> itr) {
return toValueTimestamp(itr);
return toValue(itr);
Copy link
Member Author

Choose a reason for hiding this comment

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

@apilloud I think you did the most on these models. In SQL the timestamp itself is not really observable. The next GROUP BY will have some windowing expression (or not) and the timestamp is specified according to the arguments to the windowing function.

Copy link
Contributor

@akedin akedin left a comment

Choose a reason for hiding this comment

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

LGTM

@kennknowles
Copy link
Member Author

Run Direct Runner Nexmark Tests

@kennknowles kennknowles merged commit e3c79e2 into apache:master Nov 24, 2018
@kennknowles kennknowles deleted the join-sideinput branch January 4, 2024 20:34
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.

None yet

2 participants