mihailom-db commented on PR #45285: URL: https://github.com/apache/spark/pull/45285#issuecomment-1970706405
Current SQLConf.COLLATION_ENABLED cannot be used to prevent errors of invalid collation name in TypeContext. How should I proceed with this? In my view, if customer sends a query with word COLLATE, but invalid string literal, I would expect to get back error Collation not supported before getting error of Invalid Collation name. I investigated this and am pretty sure SQLConf is not the right way to go if we want to include this config for this error. @cloud-fan @MaxGekk -- 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]
