Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/11420
We are closing it due to inactivity. please do reopen if you want to push
it forward. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/11420
Let's close this if it is not in a progress.
---
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 fe
Github user zuowang commented on the issue:
https://github.com/apache/spark/pull/11420
I'm not, could you work to resolve it?
---
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
enab
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/11420
I'm not, so it's okay to do so.
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/11420
@zuowang @maropu Are you still working on this? We should resolve this
issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/11420
@maropu Yes. We need to consider case sensitivity for the built-in data
sources at least.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11420
Can one of the admins verify this patch?
---
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 feat
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/11420
@rxin Currently, do we have any policy to handle case-sensitivity inside
spark? e.g., `postgresql` always holds names into lower case
(https://www.postgresql.org/docs/9.5/static/sql-syntax-lexical.ht
