[
https://issues.apache.org/jira/browse/HIVE-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757532#comment-13757532
]
Hive QA commented on HIVE-5203:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12601280/HIVE-5203.1.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 2909 tests executed
*Failed tests:*
{noformat}
org.apache.hcatalog.mapreduce.TestHCatExternalPartitioned.testHCatPartitionedTable
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/603/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/603/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
> FunctionRegistry.getMethodInternal() should prefer method arguments with
> closer affinity to the original argument types
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-5203
> URL: https://issues.apache.org/jira/browse/HIVE-5203
> Project: Hive
> Issue Type: Bug
> Components: Types, UDF
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: HIVE-5203.1.patch
>
>
> When the function registry is trying to determine the best version of UDF
> evaluate() to use based on a set of arguments passed in, it should prefer
> methods where the argument types are more related to the original types. For
> example if varchar is used with UDFFromUnixTime(), varchar is convertible to
> both the double and string versions of evaluate() for that UDF. In this case
> we would prefer that the function registry select the string version over the
> double version, since varchar and string are both string types.
> This doesn't really affect any of the existing types, but comes into play
> with the addition of the varchar type (HIVE-4844).
--
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
