hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-5609) possibly revisit change in unhex() behavior
Date Tue, 22 Oct 2013 19:26:44 GMT
Jason Dere created HIVE-5609:
--------------------------------

             Summary: possibly revisit change in unhex() behavior
                 Key: HIVE-5609
                 URL: https://issues.apache.org/jira/browse/HIVE-5609
             Project: Hive
          Issue Type: Bug
          Components: UDF
            Reporter: Jason Dere


Got one user case where they got bit by the change in HIVE-2482 where unhex() changed to return
Binary, where it used to return Text. Looking at the MySQL unhex() function which I'm assuming
Hive's unhex() is based on, MySQL actually returns a string value.   I know that we explicitly
document the incompatible change in the Jira, but I'd figure that most users would be using
unhex() based on how the mysql version works.  And because it's now returning binary, the
resulting value from unhex() is actually much less flexible to use if it's being nested within
other UDFs, because binary does not implicitly convert to other types.  
Is anyone open to the idea of reverting unhex() back to it's original behavior, and providing
a separate UDF to return the value as binary as [~appodictic] suggested in  HIVE-2482?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message