[
https://issues.apache.org/jira/browse/HIVE-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721342#comment-13721342
]
Hive QA commented on HIVE-4929:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12594427/HIVE-4929.patch
{color:green}SUCCESS:{color} +1 2653 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/198/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/198/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> the type of all numeric constants is changed to double in the plan
> ------------------------------------------------------------------
>
> Key: HIVE-4929
> URL: https://issues.apache.org/jira/browse/HIVE-4929
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-4929.patch
>
>
> There's code which, after the numeric type for a constant in where clause has
> been chosen as the most restricted one or based on suffix, tries to change
> the type to match the numeric column which the constant is being compared
> with. However, due to a hack from HIVE-3059 every column type shows up as
> string in that code, causing it to always change the constant type to double.
> This should not be done (regardless of the hack).
> Spinoff from HIVE-2702, large number of query outputs change so it will be a
> big patch
--
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
