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

   ## Which issue does this PR close?
   Closes https://github.com/apache/datafusion/issues/13065
   
   ## Rationale for this change
   
   Some plans that used to run in DataFusion 41.0.0 started erroring in 
DataFusion 42.0.0 due to a new check that was added.
   
   The delta-rs 42.0.0 upgrade has it this 
https://github.com/delta-io/delta-rs/pull/2886#issuecomment-2425616646, and we 
hit the same thing in InfluxDB IOx as well.
   
   To help unblock upgrades, I would like to permit users to optionally disable 
this check. 
   
   This config flag is meant to be temporary while we fix all the underlying 
bugs. 
   
   Background: a new check for exact schema equality added in 
https://github.com/apache/datafusion/pull/11989 (released in `DataFusion 
42.0.0`). This has found quite a few bugs where the schema doesn't quite match 
due to nullability or metadata mismatch -- see 
https://github.com/apache/datafusion/issues/12733. There is at least one more 
bug @wiedld  and I are tracking down. 
   
   After upgrading to DataFusion 42 some of these plans now error (due to bugs 
in DataFusion, see list on https://github.com/apache/datafusion/issues/12733)
   
   ## What changes are included in this PR?
   
   Add a `skip_physical_aggregate_schema_check` option to disable this check so 
downstream users can workaround any issues they hit
   
   ## Are these changes tested?
   
   The doc is tested by CI. Since this a workaround for bugs
   
   ## Are there any user-facing changes?
   A new config option
   <!--
   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