xudong963 opened a new pull request, #15671:
URL: https://github.com/apache/datafusion/pull/15671

   ## 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.  
   -->
   While upgrading DF46, I found tthat hese methods aren't public, but under 
some scenes, we may only need the projected schema, so it's not efficient to 
call `project()` method, which returns four elements
   ```rust
   pub fn project(&self) -> (SchemaRef, Constraints, Statistics, 
Vec<LexOrdering>) {
           if self.projection.is_none() && self.table_partition_cols.is_empty() 
{
               return (
                   Arc::clone(&self.file_schema),
                   self.constraints.clone(),
                   self.file_source.statistics().unwrap().clone(),
                   self.output_ordering.clone(),
               );
           }
   
           let schema = self.projected_schema();
           let constraints = self.projected_constraints();
           let stats = self.projected_stats();
   
           let output_ordering = get_projected_output_ordering(self, &schema);
   
           (schema, constraints, stats, output_ordering)
       }
   ```
   
   ## 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.
   -->
   
   Make the three projected methods public
   
   ## 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)?
   -->
   
   ## 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: 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

Reply via email to