I try to do it in MultiQueryOptimizerTez, there is a TODO tag for that. Actually we need to check the filter condition, cuz not filter in splittee is redundant, right?
During my debugging, I manually examined bunch of plans, I am pretty sure it should not be the case.
I can run e2e tests with mutiquery off to see.
The good thing is combiner/secondary key property is on edge. When POSplit consume a vertex A, I keep the original edge from A to its successor. So combiner/secondary key property is still there.
This is an automatically generated e-mail. To reply, visit:
On Feb. 17, 2014, 4:25 a.m., Daniel Dai wrote: