[
https://issues.apache.org/jira/browse/HIVE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726134#comment-13726134
]
Hudson commented on HIVE-4928:
------------------------------
ABORTED: Integrated in Hive-trunk-hadoop2 #319 (See
[https://builds.apache.org/job/Hive-trunk-hadoop2/319/])
HIVE-4928 : Date literals do not work properly in partition spec clause (Jason
Dere via Ashutosh Chauhan) (hashutosh:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1508534)
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/IdentifiersParser.g
*
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/TypeCheckProcFactory.java
* /hive/trunk/ql/src/test/queries/clientpositive/partition_date2.q
* /hive/trunk/ql/src/test/results/clientpositive/partition_date2.q.out
> 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
> Fix For: 0.12.0
>
> 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
