[
https://issues.apache.org/jira/browse/PHOENIX-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272582#comment-15272582
]
Hudson commented on PHOENIX-2878:
---------------------------------
SUCCESS: Integrated in Phoenix-master #1217 (See
[https://builds.apache.org/job/Phoenix-master/1217/])
PHOENIX-2878 CURRENT_TIME fails to provide correct time when projected
(maryannxue: rev 596726089a530e261aee27b7680466942a0d1b4c)
* phoenix-core/src/main/java/org/apache/phoenix/compile/StatementContext.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/DateTimeIT.java
> CURRENT_TIME fails to provide correct time when projected table is using
> ------------------------------------------------------------------------
>
> Key: PHOENIX-2878
> URL: https://issues.apache.org/jira/browse/PHOENIX-2878
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.7.0
> Reporter: Sergey Soldatov
> Assignee: Sergey Soldatov
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2878-1.patch
>
>
> When the query is using projected table, the CURRENT_TIME() function may
> return zero or outdated value. Simple test case:
> {noformat}
> CREATE TABLE T1 ( ID integer primary key);
> CREATE TABLE T2 ( ID integer primary key);
> UPSERT INTO T1 VALUES (1);
> UPSERT INTO T2 VALUES (1);
> select /*+ USE_SORT_MERGE_JOIN */ op.id, current_time() from t1 op where
> op.id in (select id from t2);
> {noformat}
> The result:
> {noformat}
> +--------+---------------------------------+
> | OP.ID | TIME '1970-01-01 00:00:00.000' |
> +--------+---------------------------------+
> | 1 | 1970-01-01 00:00:00.000 |
> +--------+---------------------------------+
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
