mustafasrepo commented on PR #4439:
URL:
https://github.com/apache/arrow-datafusion/pull/4439#issuecomment-1333344570
> @mustafasrepo Could you please explain more specifically why you can not
rely on the current `output_ordering` result? Do you have your own physical
optimizer rules?
To replicate my problem if we put the statement `println!("input exec output
ordering:{:?}", input_exec.output_ordering());
`[here](https://github.com/apache/arrow-datafusion/blob/fdc83e8524df30ac5d0ae097572b7c48dc686ba9/datafusion/core/src/physical_plan/planner.rs#L518)
For above query, we receive output ordering `input exec output
ordering:None`, for both `WindowAggExec`s
However, for the second `WindowAggExec` we should receive `input exec
output ordering:Some([PhysicalSortExpr { expr: Column { name: "c9", index: 1 },
options: SortOptions { descending: false, nulls_first: false } },
PhysicalSortExpr { expr: Column { name: "c8", index: 0 }, options: SortOptions
{ descending: false, nulls_first: false } }])`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
