beliefer opened a new pull request, #41328: URL: https://github.com/apache/spark/pull/41328
### What changes were proposed in this pull request? Project connect, from some perspectives, can be thought as replacing the SQL parser to generate a parsed (but the difference that is unresolved) plan, then the plan is passed to the analyzer. This means that connect should also do validation on the proto as there are many in-validate parser cases that analyzer does not expect to see, which potentially could cause problems if connect only pass through the proto (of course have it translated) to analyzer. Meanwhile I think this is a good idea to decouple the validation and transformation so that we have two stages: stage 1: proto validation. For example validate if necessary fields are populated or not. stage 2: transformation, which convert the proto to a plan with assumption that the plan is valid parsed version of the plan. This PR checks before transformation through a simple proxy pattern. Because there are a lot of job to do, this PR only given an example(e.g. checkReadRel). So that acilitate communication and discussion. ### Why are the changes needed? Decouple plan transformation and validation on server side ### Does this PR introduce _any_ user-facing change? 'No'. Just update the inner implementation. ### How was this patch tested? Exists test cases. -- 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]
