[I] The `limit` info lost in the AggregateExec when ser/deser the physical plan [datafusion]

[via GitHub]

liukun4515 opened a new issue, #10630:
URL: https://github.com/apache/datafusion/issues/10630

   ### Describe the bug
   
   In the definition of  `AggregateExec`, we have the `limit` argument to 
optimize the agg operation.
   
   ```
   pub struct AggregateExec {
        .....
       /// Set if the output of this aggregation is truncated by a upstream 
sort/limit clause
       limit: Option<usize>,
       .....
   }
   ```
   
   But it is not added in the .proto file, when we use the proto to ser/deser 
the agg physical node, the `limit` will lost.
   
   ### To Reproduce
   
   _No response_
   
   ### Expected behavior
   
   _No response_
   
   ### Additional context
   
   add limit option in the  proto file, and add implementation for the  `limit` 
arg in the to_proto and from_proto 


-- 
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.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