[
https://issues.apache.org/jira/browse/HIVE-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791924#comment-13791924
]
Hive QA commented on HIVE-4821:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12607851/HIVE-4821.2.patch
{color:green}SUCCESS:{color} +1 4402 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1095/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1095/console
Messages:
{noformat}
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.
> Implement vectorized type casting for all types
> -----------------------------------------------
>
> Key: HIVE-4821
> URL: https://issues.apache.org/jira/browse/HIVE-4821
> Project: Hive
> Issue Type: Sub-task
> Affects Versions: 0.13.0
> Reporter: Eric Hanson
> Assignee: Eric Hanson
> Attachments: HIVE-4821.2.patch
>
>
> Implement vectorized support for casting from any type to any type.
> From the documentation:
> cast(expr as <type>): Converts the results of the expression expr to <type>
> e.g. cast('1' as BIGINT) will convert the string '1' to it integral
> representation. A null is returned if the conversion does not succeed
> The current supported internal types are:
> LONG
> DOUBLE
> STRING
> TIMESTAMP
> Before implementation, determine what are the semantics of explicit casting
> to types less general than the internal types. E.g. what if you cast DOUBLE
> to TINYINT? Can we just cast internally to LONG and let the output process
> cast to TINYINT?
> This JIRA includes all work to make casting operate end-to-end in a SQL query
> in vectorized mode, including updates to VectorizationContext.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
