Skip to content

Conversation

@vibhatha
Copy link
Contributor

This PR includes a minor suggestion (suggestive-PR) on fixing the issue associated with obtaining the output_schema from the streaming execution plan.

@lidavidm
Copy link
Member

IMO, this isn't minor anymore - we should file a Jira.

@vibhatha
Copy link
Contributor Author

@lidavidm I will create one.

@lidavidm
Copy link
Member

The approach looks fine to me, but I thought there was some reason why we didn't want a SinkNode to technically have an output schema. @westonpace do you recall?

{"order_by_sink", OrderBySinkNodeOptions{options, &sink_gen}},
})
.AddToPlan(plan.get()));
ASSERT_EQ(plan->sources()[0]->output_schema(), plan->sinks()[0]->output_schema());
Copy link
Member

Choose a reason for hiding this comment

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

Is it possible to just add these checks to existing tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes we can. I separated it in case it diverts from the purpose. There is code duplication with the current approach.

@westonpace
Copy link
Member

Hmm, I don't, but thinking about it now I guess I can kind of see why it is this way. Technically the sink node has no outputs so there is no input schema. I suppose what we really want is for the sink consumer to access the schema of the input node. Take a look at #12721 and see if that might be a better approach.

@vibhatha
Copy link
Contributor Author

@westonpace @lidavidm let's close this PR. I am +1 for #12721

@vibhatha
Copy link
Contributor Author

Closing this PR inplace of #12721

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.

3 participants