Skip to content

Conversation

@sharkovadarya
Copy link
Collaborator

This is, like, disappointingly void of substance. Sorry.

So, as we discussed, we want to have a separate pipeline that would accept user queries, submit them to the coordinator to create the pipeline, then submit that pipeline to the executor, which would send it to the cluster. That separate pipeline would be CoordinatorExecutorPipeline. For now, planner, queryPlanner, etc are left as parameters, seeing as I don't know how to obtain their instances (for example, apparently, the instance of CalciteQueryPlanner that's used when executing a SQL query in Beam is instantiated by BeamSqlEnv using reflection, if the code comments are to be believed? How do we get /that/...), although ideally I assume the only things that the user would need to supply are query jobs and inputs.

I tried to test whether it works, but, alas, that would require me to find an UnboundedSource to register... should I have used the Nexmark one?

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.

2 participants