You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Xinyi Yan (Jira)" <ji...@apache.org> on 2019/08/27 06:53:00 UTC
[jira] [Updated] (PHOENIX-5453) incorrect metadata caused by
`CREATE INDEX`
[ https://issues.apache.org/jira/browse/PHOENIX-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xinyi Yan updated PHOENIX-5453:
-------------------------------
Description:
{code:java}
CREATE TABLE BASETABLE (A BIGINT PRIMARY KEY, B BIGINT, C BIGINT);
0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(1,1,1);
1 row affected (0.092 seconds)
0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(2,2,2);
1 row affected (0.006 seconds)
0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(3,3,3);
1 row affected (0.006 seconds)
0: jdbc:phoenix:> CREATE VIEW VIEW_TEST AS SELECT * FROM BASETABLE WHERE A > 1;
No rows affected (0.141 seconds)
0: jdbc:phoenix:> CREATE INDEX INDEX_TESTING ON VIEW_TEST(B) INCLUDE(C);
2 rows affected (5.992 seconds)
0: jdbc:phoenix:> SELECT * FROM INDEX_TESTING;
+------+----------------------+-----+
| 0:B | :A | 0:C |
+------+----------------------+-----+
| null | -9223372036842126592 | 2 |
| null | -9223372036842126336 | 3 |
+------+----------------------+-----+
2 rows selected (0.072 seconds)
{code}
While I was testing one of the Jiras on the master branch, I found this `CREATE INDEX` issue on the master branch.
Local env:
Hadoop 2.7.7
HBase 2.0
Phoenix built from the master branch.
was:
{code:java}
CREATE TABLE BASETABLE (A BIGINT PRIMARY KEY, B BIGINT, C BIGINT);
0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(1,1,1);
1 row affected (0.092 seconds)
0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(2,2,2);
1 row affected (0.006 seconds)
0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(3,3,3);
1 row affected (0.006 seconds)
0: jdbc:phoenix:> CREATE VIEW VIEW_TEST AS SELECT * FROM BASETABLE WHERE A > 1;
No rows affected (0.141 seconds)
0: jdbc:phoenix:> CREATE INDEX INDEX_TESTING ON VIEW_TEST(B) INCLUDE(C);
2 rows affected (5.992 seconds)
0: jdbc:phoenix:> SELECT * FROM INDEX_TESTING;
+------+----------------------+-----+
| 0:B | :A | 0:C |
+------+----------------------+-----+
| null | -9223372036842126592 | 2 |
| null | -9223372036842126336 | 3 |
+------+----------------------+-----+
2 rows selected (0.072 seconds)
{code}
> incorrect metadata caused by `CREATE INDEX`
> ---------------------------------------------
>
> Key: PHOENIX-5453
> URL: https://issues.apache.org/jira/browse/PHOENIX-5453
> Project: Phoenix
> Issue Type: Bug
> Reporter: Xinyi Yan
> Priority: Major
>
>
> {code:java}
> CREATE TABLE BASETABLE (A BIGINT PRIMARY KEY, B BIGINT, C BIGINT);
> 0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(1,1,1);
> 1 row affected (0.092 seconds)
> 0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(2,2,2);
> 1 row affected (0.006 seconds)
> 0: jdbc:phoenix:> UPSERT INTO BASETABLE VALUES(3,3,3);
> 1 row affected (0.006 seconds)
> 0: jdbc:phoenix:> CREATE VIEW VIEW_TEST AS SELECT * FROM BASETABLE WHERE A > 1;
> No rows affected (0.141 seconds)
> 0: jdbc:phoenix:> CREATE INDEX INDEX_TESTING ON VIEW_TEST(B) INCLUDE(C);
> 2 rows affected (5.992 seconds)
> 0: jdbc:phoenix:> SELECT * FROM INDEX_TESTING;
> +------+----------------------+-----+
> | 0:B | :A | 0:C |
> +------+----------------------+-----+
> | null | -9223372036842126592 | 2 |
> | null | -9223372036842126336 | 3 |
> +------+----------------------+-----+
> 2 rows selected (0.072 seconds)
> {code}
>
> While I was testing one of the Jiras on the master branch, I found this `CREATE INDEX` issue on the master branch.
> Local env:
> Hadoop 2.7.7
> HBase 2.0
> Phoenix built from the master branch.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)