[I] Remove input_schema from AggregateExec [arrow-datafusion]

["viirya (via GitHub)" <gi...@apache.org>]

viirya opened a new issue, #7728:
URL: https://github.com/apache/arrow-datafusion/issues/7728

   ### Is your feature request related to a problem or challenge?
   
   As we integrate `AggregateExec`, one thing confusing me is why `AggregateExec` keeps a separate `input_schema` which is not actually schema of input operator, but is always the schema of input of aggregation. In other words, partial and final aggregation operators have the same input schema parameter. It doesn't look consistent on `input_schema` and `input` functions on the operator and other operators. And another look at this `input_schema` parameter, it doesn't look like there is any meaningful usage of it. It causes a bit strange when we integrate Spark with DataFusion's aggregation operator.
   
   
   ### Describe the solution you'd like
   
   _No response_
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### Additional context
   
   _No response_


-- 
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-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Remove input_schema from AggregateExec [arrow-datafusion]

["viirya (via GitHub)" <gi...@apache.org>]

viirya closed issue #7728: Remove input_schema from AggregateExec
URL: https://github.com/apache/arrow-datafusion/issues/7728


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org