-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
distsql: processor implementation checklist #7587
Comments
taking on Sort.
|
taking on Aggregation (#9793). |
I have some partial work done on a merge-join processor, I will continue work on that when the work around tracing stuff dies down. |
taking on
|
Implementation of the `Evaluator` processor core type, a fully programmable no-grouping aggregator that runs a 'program' on each individual row. The 'program' is a set of expressions evaluated in order, the results of evaluating each of these expressions on the input row form the output. Part of cockroachdb#7587.
Implementation of the `Evaluator` processor core type, a fully programmable no-grouping aggregator that runs a 'program' on each individual row. The 'program' is a set of expressions evaluated in order, the results of evaluating each of these expressions on the input row form the output. Part of cockroachdb#7587.
Implementation of the `Evaluator` processor core type, a fully programmable no-grouping aggregator that runs a 'program' on each individual row. The 'program' is a set of expressions evaluated in order, the results of evaluating each of these expressions on the input row form the output. Part of cockroachdb#7587.
taking on @RaduBerinde also re: merge-join processor work, will take it on as soon as the partial work you mentioned is up. |
taking on Join next, taking over from #10054. |
Added Limit to the list. |
@RaduBerinde: how about |
It's there, as a "no-op" processor (NoopCoreSpec). |
This issue tracks implementation of various processor "core" types:
EvalCtx
(distsql: expressions requiring theEvalCtx
can't be evaluated #13821)The text was updated successfully, but these errors were encountered: