aokolnychyi commented on PR #53143: URL: https://github.com/apache/spark/pull/53143#issuecomment-3573662091
I think we concluded that detecting changes in tables shouldn't fail recaching. I am still debating whether we should let the following continue to fail as before: ``` sessionWithConfigsOff.sessionState.executePlan(refreshedPlan) ``` Compared to 4.0, this is the only behavior change. In 4.0, this would fail recaching (wherever it is called). In 4.1, this would NOT throw any exception, just log a warning. Thoughts, @cloud-fan @dongjoon-hyun? Are you guys OK with the PR as is? -- 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]
