[
https://issues.apache.org/jira/browse/DRILL-6414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476002#comment-16476002
]
Paul Rogers commented on DRILL-6414:
------------------------------------
A system/session option means that the change will impact all readers and
operators. We've replaced a single problem with many problems. Suppose we have
the a/A JSON query above. The option must be on.
But suppose I have a JDBC query:
{noformat}
SELECT A, B FROM `someTable`
{noformat}
The above follows the JDBC rules: case insensitive. So, the option must be off.
Now, define a view in which I join the two tables. The option must be on in one
branch, off in another.
Then, put the join or queries in a view. The user must know whether to turn the
option on or off for each view. And, as we say, for some views, the option must
be both on and off.
How will simply adding an option, and pushing the problem onto the user, solve
the above issues?
We already have similar issues, by the way, with JSON system options.
Alternative: make the setting part of the format/storage plugin config, then
work out rules for how the case sensitivity follow the name up the DAG.
> Allow Case Insensitive Comparisons in Drill
> -------------------------------------------
>
> Key: DRILL-6414
> URL: https://issues.apache.org/jira/browse/DRILL-6414
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Volodymyr Tkach
> Assignee: Volodymyr Tkach
> Priority: Major
>
> Lets take a case:
> Table t1 with column c1 having a value 'abc'
> For a query like below drill should treat the comparison as case insensitive
> and return 1 row.
> This is not an issue but we need to know if we can set case insensitivity at
> system level.
> select * from t1 where c1 = 'ABC'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
