Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -989,7 +989,11 @@ VeloxQueryPlanConverterBase::toVeloxQueryPlan(
bool streamable = !node->preGroupedVariables.empty() &&
node->groupingSets.groupingSetCount == 1 &&
node->groupingSets.globalGroupingSets.empty();

// TODO karteekmurthys@ Re-enable after
// fixing:https://github.com/prestodb/presto/issues/22585
if (streamable) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

sorry for all the back and forth. instead of failing in plan conversion for aggregation as you are doing here, can we fail in plan conversion for join if it's a nested loop join? That would be a more robust mitigation because it's the root cause of the issue, and there are other optimizations aside from streaming aggregation that might be assuming nested loop join is preserving order when it's not e.g. we might remove an order by because we think the input is already ordered or plan a merge join because we think the input is ordered.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

FYI I am turning off NLJ here : #23341 .

VELOX_UNSUPPORTED("StreamingAggregation is not supported");
}
// groupIdField and globalGroupingSets are required for producing default
// output rows for global grouping sets when there are no input rows.
// Global grouping sets can be present without groupIdField in Final
Expand Down