juliuszsompolski commented on pull request #34453: URL: https://github.com/apache/spark/pull/34453#issuecomment-995617438
> It's up to our decision, but it's safe to keep the existing behavior first and to switch it at next version because it gives the users a chance to try this new behavior. My 2cents: working with various partners and vendors of BI tools, we found GetFunctions to rarely be used at all, and when we found it used, it was in the context of the current behaviour causing trouble (running to slow, causing UI freezes because of trying to render the humongous list of duplicated functions). I am not aware of any tool depending on the current behaviour. Note that before GetTables / GetSchemas / GetColumns gotten implemented in Spark 3.0, this was all throwing wrong results or errors with Spark, and it has not been escalated for a long time. Only recently BI vendors are picking up serious interest in developing connectors that take advantage of these functions, and this has been reported as something that is an unexpected and unwanted behaviour. -- 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]
