[
https://issues.apache.org/jira/browse/HIVE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722084#comment-13722084
]
Hive QA commented on HIVE-4928:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12594613/HIVE-4928.D11871.1.patch
{color:green}SUCCESS:{color} +1 2736 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/218/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/218/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.
> Date literals do not work properly in partition spec clause
> -----------------------------------------------------------
>
> Key: HIVE-4928
> URL: https://issues.apache.org/jira/browse/HIVE-4928
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: HIVE-4928.1.patch.txt, HIVE-4928.D11871.1.patch
>
>
> The partition spec parsing doesn't do any actual real evaluation of the
> values in the partition spec, instead just taking the text value of the
> ASTNode representing the partition value. This works fine for string/numeric
> literals (expression tree below):
> (TOK_PARTVAL region 99)
> But not for Date literals which are of form DATE 'yyyy-mm-dd' (expression
> tree below:
> (TOK_DATELITERAL '1999-12-31')
> In this case the parser/analyzer uses "TOK_DATELITERAL" as the partition
> column value, when it should really get value of the child of the DATELITERAL
> token.
--
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
