Github user jackylk commented on the pull request:
https://github.com/apache/spark/pull/3558#issuecomment-65892057
If we go for second way, it will create cyclic dependency between
spark-catalyst and spark-sql sub-projects, because SQLConf and SQLContext is in
spark-sql while Analyzer is in spark-catalyst.
I think the current way the only drawback is that caseSensitive can only be
set while initializing SQLContext, but can not be set after initialization. If
client want to use case insensitive analyzer, he need to create a new
SQLContext, which I think it is probably OK.
I tested this way locally and it is passing SQLQuerySuite, I do not know
why test case failed, as I can not access Jenkins test report now. Can anyone
trigger Jenkins again, thanks.
And any more suggestion for better solution?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
