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

   ## 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 #22935.
   
   ## Rationale for this change
   
   Anonymous file reads can read the same path with different explicit schemas 
in the same session. The shared file statistics cache was keyed by table/path 
metadata, but did not validate that cached statistics matched the schema used 
to compute them.
   
   This could reuse narrower cached statistics for a later wider schema read 
and panic during statistics projection.
   
   <!--
    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.  
   -->
   
   ## What changes are included in this PR?
   
   This PR routes anonymous listing table statistics through a per-table cache 
instead of the shared session cache.
   
   Named tables still use the shared session cache, since their table reference 
gives the cache a stable identity.
   
   It also adds a regression test that first warms statistics with the physical 
schema, then reads the same Parquet file with a wider explicit schema.
   
   <!--
   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?
   
   Yes
   
   <!--
   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?
   
   No API Change
   
   <!--
   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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to