Description
Right now, SQL's mutable projection updates every value of the mutable project after it evaluates the corresponding expression. This makes the behavior of MutableProjection confusing and complicate the implementation of common aggregate functions like stddev because developers need to be aware that when evaluating {{i+1}}th expression of a mutable projection, {{i}}th slot of the mutable row has already been updated.
A better behavior of MutableProjection will be that we evaluate all expressions first and then update all values of the mutable row.
Attachments
Issue Links
- links to