[
https://issues.apache.org/jira/browse/HIVE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666278#comment-13666278
]
John Omernik commented on HIVE-4070:
------------------------------------
What about this? Leave it case sensitive as it is, but provide a HIVE Variable
that allows it to be set globally. That way, an administrator can set the
behaivior of LIKE based on what their users are migrating in from. I.e. if
MSSQL or MYSQL then set it to be case insensitive, else use the default of
case sensitive. The issue here is one of transitioning and potential false
negatives because of the assumption. Correct, you can't be consistent with
every SQL implementation out there, however, I think there is some precedence
for being LIKE '%mySql%'(see what I did there) which is case insensitive by
default.
> Like operator in Hive is case sensitive while in MySQL (and most likely other
> DBs) it's case insensitive
> --------------------------------------------------------------------------------------------------------
>
> Key: HIVE-4070
> URL: https://issues.apache.org/jira/browse/HIVE-4070
> Project: Hive
> Issue Type: Bug
> Components: UDF
> Affects Versions: 0.10.0
> Reporter: Mark Grover
> Assignee: Mark Grover
> Priority: Trivial
>
> Hive's like operator seems to be case sensitive.
> See
> https://github.com/apache/hive/blob/trunk/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFLike.java#L164
> However, MySQL's like operator is case insensitive. I don't have other DB's
> (like PostgreSQL) installed and handy but I am guessing their LIKE is case
> insensitive as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
