[ https://issues.apache.org/jira/browse/HIVE-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760886#comment-13760886 ]
Hudson commented on HIVE-5204: ------------------------------ FAILURE: Integrated in Hive-trunk-hadoop2-ptest #85 (See [https://builds.apache.org/job/Hive-trunk-hadoop2-ptest/85/]) HIVE-5204 : Change type compatibility methods to use PrimitiveCategory rather than TypeInfo (Jason Dere via Ashutosh Chauhan) (hashutosh: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1520707) * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/FunctionRegistry.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFBaseCompare.java * /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/exec/TestFunctionRegistry.java > Change type compatibility methods to use PrimitiveCategory rather than > TypeInfo > ------------------------------------------------------------------------------- > > Key: HIVE-5204 > URL: https://issues.apache.org/jira/browse/HIVE-5204 > Project: Hive > Issue Type: Improvement > Reporter: Jason Dere > Assignee: Jason Dere > Attachments: HIVE-5204.1.patch, HIVE-5204.2.patch, > HIVE-5204.D12687.1.patch > > > The type compatibility methods in the FunctionRegistry (getCommonClass, > implicitConvertable) compare TypeInfo objects directly when its doing its > type compatibility logic. This won't work as well with qualified types > (varchar, char, decimal), because we will need different TypeInfo objects to > represent varchar(5) and varchar(10), and the equality comparisons won't work > anymore. We can change this logic to look at the PrimitiveCategory for the > TypeInfo instead. -- 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