ahmetenis opened a new pull request, #9125:
URL: https://github.com/apache/arrow-datafusion/pull/9125

   ## Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   Closes #.
   
   ## Rationale for this change
   
   <!--
    Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.  
   -->
   In the default configuration, the naive planner frequently employs the 
`SortExec` mechanism to ensure data is correctly ordered. This `SortExec` 
utilization poses a challenge, particularly in streaming environments. The 
inherent nature of `SortExec` demands access to the entire dataset for sorting, 
a requirement in conflict with the streaming model, which processes data in 
chunks rather than as a whole.
   
   However, if a table has an order like `[a ASC, b ASC]` and a lexicographical 
sort of `[a ASC, b ASC, d ASC]` is needed, the `d` column might be sorted 
without accessing the whole dataset in many practical cases.
   
   The primary objective is to optimize the naive planner to eliminate the 
necessity of materializing the entire dataset with `SortExec`, especially in 
streaming scenarios and certain use cases.
   
   ## What changes are included in this PR?
   
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   
   ## Are these changes tested?
   
   <!--
   We typically require tests for all PRs in order to:
   1. Prevent the code from being accidentally broken by subsequent changes
   2. Serve as another way to document the expected behavior of the code
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   - Unit tests added for enforce_sorting subrule replacing SortExec plan with 
PartialSortExec plan
   - Unit tests added for PartialSortExec
   
   ## Are there any user-facing changes?
   
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->
   


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

Reply via email to