Closed eddyxu closed 2 years ago
It is difficult to make SparkSessionExtensions
to ingest a rule to handle this at the moment.
SparkSessionExtensions.ingestResolutionRule
happens AFTER spark sql parser raises the error of #332 .
To completely fix this, we should do it in upstream:
Partially mitigate #332.