vegarsti commented on code in PR #16985:
URL: https://github.com/apache/datafusion/pull/16985#discussion_r2243466485
##########
datafusion/physical-plan/src/unnest.rs:
##########
@@ -101,8 +101,22 @@ impl UnnestExec {
input: &Arc<dyn ExecutionPlan>,
schema: SchemaRef,
) -> PlanProperties {
+ // Extract equivalence properties from input plan
+ let input_eq_properties = input.equivalence_properties();
+ let input_oeq_class = input_eq_properties.oeq_class();
+ let orderings = input_oeq_class.orderings().to_vec();
+ let eq_group = input_eq_properties.eq_group();
+ let constraints = input_eq_properties.constraints();
+
Review Comment:
In the UnnestExec, we have `list_column_indices: Vec<ListUnnest>` and
`struct_column_indices: Vec<usize>`. What I don't know is whether we need to
explicitly remove these from the new `EquivalenceProperties` object, or
whether that happens "automatically", or whether it doesn't hurt that they are
there.
--
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: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
