[
https://issues.apache.org/jira/browse/HIVE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666844#comment-13666844
]
John Omernik commented on HIVE-4070:
------------------------------------
Edward and Mark: Can you please explain risky (from a programming PoV)in the
situations you are talking about? I am not a programmer, so I am looking at
this from both and end-user and from the point of view of an organization that
is going to implement Hive to assist with business decisions.
When I see the two risks, i.e. my understanding of the programming risk (Which
I am admitting I have very little understanding, hence the asking for the
explanation) vs. the implementation risk i.e. organizations that are migrating
to Hive, I worry that those decisions, which are based on false negatives
because of the current choices (case sensitivity), could be very bad from a
business/implementation risk standpoint.
Please do not take my persistent questioning as being combative, I am just
trying to look at this purely from a user/organization point of view. I.e.
training people to do things different, the results from poor training or
employee turnover, etc causing these false negatives on data. There has to be
an elegant way to give the organization control over this... even documenting
such a setting for administrators is nice, but it still relies on user
training/choices to ensure business decisions are not based on false negatives.
If we had a setting we could change, we could point out the difference, and
give users/org and option that fits with each org's use case.
As I said, just trying to understand about the risk on the programming side, I
see the risk, as a power user, administrator etc as having a high likelihood of
occurring, and the impact of said risk (false negatives) as being high as well.
That said, I defer to you guys on the programming side.
> 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
