averyqi-db commented on PR #48127: URL: https://github.com/apache/spark/pull/48127#issuecomment-2360192292
> no matter Spark is case-sensitive or not, it must be case-preserving. We need to fix the optimizer rule that breaks case-preserving. I see. But for this case, `AggregatePushThroughJoins` are case-preserving, the generated Project operator and AggregatePart operator are generated using existing Aggregate schema. For this case, the validateSchemaOutput does incur a false alarm. I can try to think of another way to erase this false alarm. :) -- 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]
