[ 
https://issues.apache.org/jira/browse/HIVE-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816368#comment-13816368
 ] 

Hive QA commented on HIVE-5564:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12612624/HIVE-5564.3.patch

{color:green}SUCCESS:{color} +1 4587 tests passed

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/182/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/182/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.

ATTACHMENT ID: 12612624

> Need to accomodate table decimal columns that were defined prior to HIVE-3976
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-5564
>                 URL: https://issues.apache.org/jira/browse/HIVE-5564
>             Project: Hive
>          Issue Type: Task
>          Components: Types
>    Affects Versions: 0.13.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>             Fix For: 0.13.0
>
>         Attachments: HIVE-5564.1.patch, HIVE-5564.2.patch, HIVE-5564.3.patch, 
> HIVE-5564.patch
>
>
> With HIVE-3976, decimal columns are stored with precision/scale, such as 
> decimal(17,5), as the type name. However, such columns defined in hive prior 
> to HIVE-3976 have a name as "decimal". Those columns need to continue to work 
> with a precision/scale as (10,0), per the functional doc. With patch in 
> HIVE-3976, we may get the following error message in such case:
> {code}
> 0: jdbc:hive2://localhost:10000> desc dec;
> Error: Error while processing statement: FAILED: RuntimeException Decimal 
> type is specified without length: decimal:int (state=42000,code=40000)
> {code}
> This issue will be addressed in this JIRA as a follow-up task.



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

Reply via email to