[jira] [Updated] (PHOENIX-6669) RVC returns a wrong result
[
https://issues.apache.org/jira/browse/PHOENIX-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6669:
---
Description:
{code:java}
CREATE TABLE IF NOT EXISTS DUMMY (
PK1 VARCHAR NOT NULL,
PK2 BIGINT NOT NULL,
PK3 BIGINT NOT NULL,
PK4 VARCHAR NOT NULL,
COL1 BIGINT,
COL2 INTEGER,
COL3 VARCHAR,
COL4 VARCHAR, CONSTRAINT PK PRIMARY KEY
(
PK1,
PK2,
PK3,
PK4
)
);UPSERT INTO DUMMY (PK1, PK4, COL1, PK2, COL2, PK3, COL3, COL4)
VALUES ('xx', 'xid1', 0, 7, 7, 7, 'INSERT', null);
{code}
The non-RVC query returns no row, but the RVC query returns a wrong result.
{code:java}
0: jdbc:phoenix:localhost> select PK2
. . . . . . . . . . . . .> from DUMMY
. . . . . . . . . . . . .> where PK1 ='xx'
. . . . . . . . . . . . .> and (PK1 > 'xx' AND PK1 <= 'xx')
. . . . . . . . . . . . .> and (PK2 > 5 AND PK2 <=5)
. . . . . . . . . . . . .> and (PK3 > 2 AND PK3 <=2);
+--+
| PK2 |
+--+
+--+
No rows selected (0.022 seconds)
0: jdbc:phoenix:localhost> select PK2
. . . . . . . . . . . . .> from DUMMY
. . . . . . . . . . . . .> where (PK1 = 'xx')
. . . . . . . . . . . . .> and (PK1, PK2, PK3) > ('xx', 5, 2)
. . . . . . . . . . . . .> and (PK1, PK2, PK3) <= ('xx', 5, 2);
+--+
| PK2 |
+--+
| 7 |
+--+
1 row selected (0.033 seconds) {code}
{code:java}
0: jdbc:phoenix:localhost> EXPLAIN select PK2 from DUMMY where (PK1 = 'xx') and
(PK1, PK2, PK3) > ('xx', 5, 2) and (PK1, PK2, PK3) <= ('xx', 5, 2);
+--+--+--+--+
| PLAN | EST_BYTES_READ
| EST_ROWS_READ | |
+--+--+--+--+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['xx'] | null
| null |
| SERVER FILTER BY FIRST KEY ONLY | null
| null | |
+--+--+--+--+
2 rows selected (0.024 seconds)
0: jdbc:phoenix:localhost> explain select PK2 from DUMMY where PK1 ='xx' and
(PK1 > 'xx' AND PK1 <= 'xx') and (PK2 > 5 AND PK2 <=5) and (PK3 > 2 AND PK3
<=2);
+--+--+--+--+
| PLAN | EST_BYTES_READ
| EST_ROWS_READ | |
+--+--+--+--+
| DEGENERATE SCAN OVER DUMMY | null
| null | |
+--+--+--+--+
1 row selected (0.015 seconds){code}
was:
{code:java}
CREATE TABLE IF NOT EXISTS DUMMY (
PK1 VARCHAR NOT NULL,
PK2 BIGINT NOT NULL,
PK3 BIGINT NOT NULL,
PK4 VARCHAR NOT NULL,
COL1 BIGINT,
COL2 INTEGER,
COL3 VARCHAR,
COL4 VARCHAR, CONSTRAINT PK PRIMARY KEY
(
PK1,
PK2,
PK3,
PK4
)
);UPSERT INTO DUMMY (PK1, PK4, COL1, PK2, COL2, PK3, COL3, COL4)
VALUES ('xx', 'xid1', 0, 7, 7, 7, 'INSERT', null);
{code}
The non-RVC query returns no row, but the RVC query returns a wrong result.
{code:java}
0: jdbc:phoenix:localhost> select PK2
. . . . . . . . . . . . .> from DUMMY
. . . . . . . . . . . . .> where (PK1 = 'xx')
. . . . . . . . . . . . .> and ((PK2 > 5 AND PK2 <=5))
. . . . . . . . . . . . .> and ((PK3 > 2 AND PK3 <=2));
+--+
| PK2 |
+--+
+--+
No rows selected (0.022 seconds)
0: jdbc:phoenix:localhost> select PK2
. . . . . . . . . . . . .> from DUMMY
. . . . . . . . . . . . .> where (PK1 = 'xx')
. . . . . . . . . . . . .> and (PK1, PK2, PK3) > ('xx', 5, 2)
. . . . . . . . . . . . .> and (PK1, PK2, PK3) <= ('xx', 5, 2);
+--+
| PK2 |
[jira] [Created] (PHOENIX-6669) RVC returns a wrong result
Xinyi Yan created PHOENIX-6669:
--
Summary: RVC returns a wrong result
Key: PHOENIX-6669
URL: https://issues.apache.org/jira/browse/PHOENIX-6669
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.16.1
Reporter: Xinyi Yan
{code:java}
CREATE TABLE IF NOT EXISTS DUMMY (
PK1 VARCHAR NOT NULL,
PK2 BIGINT NOT NULL,
PK3 BIGINT NOT NULL,
PK4 VARCHAR NOT NULL,
COL1 BIGINT,
COL2 INTEGER,
COL3 VARCHAR,
COL4 VARCHAR, CONSTRAINT PK PRIMARY KEY
(
PK1,
PK2,
PK3,
PK4
)
);UPSERT INTO DUMMY (PK1, PK4, COL1, PK2, COL2, PK3, COL3, COL4)
VALUES ('xx', 'xid1', 0, 7, 7, 7, 'INSERT', null);
{code}
The non-RVC query returns no row, but the RVC query returns a wrong result.
{code:java}
0: jdbc:phoenix:localhost> select PK2
. . . . . . . . . . . . .> from DUMMY
. . . . . . . . . . . . .> where (PK1 = 'xx')
. . . . . . . . . . . . .> and ((PK2 > 5 AND PK2 <=5))
. . . . . . . . . . . . .> and ((PK3 > 2 AND PK3 <=2));
+--+
| PK2 |
+--+
+--+
No rows selected (0.022 seconds)
0: jdbc:phoenix:localhost> select PK2
. . . . . . . . . . . . .> from DUMMY
. . . . . . . . . . . . .> where (PK1 = 'xx')
. . . . . . . . . . . . .> and (PK1, PK2, PK3) > ('xx', 5, 2)
. . . . . . . . . . . . .> and (PK1, PK2, PK3) <= ('xx', 5, 2);
+--+
| PK2 |
+--+
| 7 |
+--+
1 row selected (0.033 seconds) {code}
{code:java}
0: jdbc:phoenix:localhost> EXPLAIN select PK2 from DUMMY where (PK1 = 'xx') and
(PK1, PK2, PK3) > ('xx', 5, 2) and (PK1, PK2, PK3) <= ('xx', 5, 2);
+--+--+--+--+
| PLAN | EST_BYTES_READ
| EST_ROWS_READ | |
+--+--+--+--+
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['xx'] | null
| null |
| SERVER FILTER BY FIRST KEY ONLY | null
| null | |
+--+--+--+--+
2 rows selected (0.024 seconds)
0: jdbc:phoenix:localhost> EXPLAIN select PK2 from DUMMY where (PK1 = 'xx') and
((PK2 > 5 AND PK2 <=5)) and ((PK3 > 2 AND PK3 <=2));
+--+--+--+--+
| PLAN | EST_BYTES_READ
| EST_ROWS_READ | |
+--+--+--+--+
| DEGENERATE SCAN OVER DUMMY | null
| null | |
+--+--+--+--+
1 row selected (0.005 seconds) {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (PHOENIX-6662) Failed to delete rows when PK has one or more DESC column with IN clause
[
https://issues.apache.org/jira/browse/PHOENIX-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan resolved PHOENIX-6662.
Resolution: Fixed
> Failed to delete rows when PK has one or more DESC column with IN clause
>
>
> Key: PHOENIX-6662
> URL: https://issues.apache.org/jira/browse/PHOENIX-6662
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Assignee: Gokcen Iskender
>Priority: Critical
>
> Global connection to create a base table and view.
> {code:java}
> CREATE TABLE IF NOT EXISTS DUMMY.BASE (TETNANT_ID CHAR(15) NOT NULL, PREFIX
> CHAR(3) NOT NULL, COL1 DATE, COL2 CHAR(15), COL3 DATE, COL4 CHAR(15), COL5
> DATE CONSTRAINT PK PRIMARY KEY ( TETNANT_ID, PREFIX ) ) MULTI_TENANT=true;
> CREATE VIEW IF NOT EXISTS DUMMY.GLOBAL_VIEW (PK1 DECIMAL(12, 3) NOT NULL,
> PK2 BIGINT NOT NULL, COL6 CHAR(15) , COL7 DATE, COL8 BOOLEAN, COL9 CHAR(15),
> COL10 VARCHAR, COL11 VARCHAR CONSTRAINT PKVIEW PRIMARY KEY (PK1 DESC, PK2))
> AS SELECT * FROM DUMMY.BASE WHERE PREFIX = '01A'; {code}
> Tenant connection to create a view and repro the issue
> {code:java}
> 0: jdbc:phoenix:localhost> CREATE VIEW DUMMY."0ph" AS SELECT * FROM
> DUMMY.GLOBAL_VIEW;
> No rows affected (0.055 seconds)
> 0: jdbc:phoenix:localhost> UPSERT INTO DUMMY."0ph" (PK1,PK2) VALUES (10.0,10);
> 1 row affected (0.038 seconds)
> 0: jdbc:phoenix:localhost> UPSERT INTO DUMMY."0ph" (PK1,PK2) VALUES (20.0,20);
> 1 row affected (0.008 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY."0ph";
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | PREFIX | COL1 | COL2 | COL3
> | COL4 | COL5 | PK1 |
> PK2 | COL6 | COL7 |
> COL8 | COL9 | COL |
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | 01A | null | | null
> | | null | 2E+1 | 20
> | | null |
> | | |
> | 01A | null | | null
> | | null | 1E+1 | 10
> | | null |
> | | |
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> 2 rows selected (0.035 seconds)
> 0: jdbc:phoenix:localhost> DELETE FROM DUMMY."0ph" WHERE (PK1,PK2) IN
> ((10.0,10),(20.0,20));
> No rows affected (0.024 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY."0ph";
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | PREFIX | COL1 | COL2 | COL3
> | COL4 | COL5 | PK1 |
> PK2 | COL6 | COL7 |
> COL8 | COL9 | COL |
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | 01A | null | | null
> | | null | 2E+1 | 20
>
[jira] [Assigned] (PHOENIX-6662) Failed to delete rows when PK has one or more DESC column with IN clause
[
https://issues.apache.org/jira/browse/PHOENIX-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan reassigned PHOENIX-6662:
--
Assignee: Gokcen Iskender
> Failed to delete rows when PK has one or more DESC column with IN clause
>
>
> Key: PHOENIX-6662
> URL: https://issues.apache.org/jira/browse/PHOENIX-6662
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Assignee: Gokcen Iskender
>Priority: Critical
>
> Global connection to create a base table and view.
> {code:java}
> CREATE TABLE IF NOT EXISTS DUMMY.BASE (TETNANT_ID CHAR(15) NOT NULL, PREFIX
> CHAR(3) NOT NULL, COL1 DATE, COL2 CHAR(15), COL3 DATE, COL4 CHAR(15), COL5
> DATE CONSTRAINT PK PRIMARY KEY ( TETNANT_ID, PREFIX ) ) MULTI_TENANT=true;
> CREATE VIEW IF NOT EXISTS DUMMY.GLOBAL_VIEW (PK1 DECIMAL(12, 3) NOT NULL,
> PK2 BIGINT NOT NULL, COL6 CHAR(15) , COL7 DATE, COL8 BOOLEAN, COL9 CHAR(15),
> COL10 VARCHAR, COL11 VARCHAR CONSTRAINT PKVIEW PRIMARY KEY (PK1 DESC, PK2))
> AS SELECT * FROM DUMMY.BASE WHERE PREFIX = '01A'; {code}
> Tenant connection to create a view and repro the issue
> {code:java}
> 0: jdbc:phoenix:localhost> CREATE VIEW DUMMY."0ph" AS SELECT * FROM
> DUMMY.GLOBAL_VIEW;
> No rows affected (0.055 seconds)
> 0: jdbc:phoenix:localhost> UPSERT INTO DUMMY."0ph" (PK1,PK2) VALUES (10.0,10);
> 1 row affected (0.038 seconds)
> 0: jdbc:phoenix:localhost> UPSERT INTO DUMMY."0ph" (PK1,PK2) VALUES (20.0,20);
> 1 row affected (0.008 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY."0ph";
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | PREFIX | COL1 | COL2 | COL3
> | COL4 | COL5 | PK1 |
> PK2 | COL6 | COL7 |
> COL8 | COL9 | COL |
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | 01A | null | | null
> | | null | 2E+1 | 20
> | | null |
> | | |
> | 01A | null | | null
> | | null | 1E+1 | 10
> | | null |
> | | |
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> 2 rows selected (0.035 seconds)
> 0: jdbc:phoenix:localhost> DELETE FROM DUMMY."0ph" WHERE (PK1,PK2) IN
> ((10.0,10),(20.0,20));
> No rows affected (0.024 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY."0ph";
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | PREFIX | COL1 | COL2 | COL3
> | COL4 | COL5 | PK1 |
> PK2 | COL6 | COL7 |
> COL8 | COL9 | COL |
> ++-+-+-+-+-+--+--+-+-+--+-+--+
> | 01A | null | | null
> | | null | 2E+1 | 20
[jira] [Updated] (PHOENIX-6662) Failed to delete rows when PK has one or more DESC column with IN clause
[
https://issues.apache.org/jira/browse/PHOENIX-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6662:
---
Description:
Global connection to create a base table and view.
{code:java}
CREATE TABLE IF NOT EXISTS DUMMY.BASE (TETNANT_ID CHAR(15) NOT NULL, PREFIX
CHAR(3) NOT NULL, COL1 DATE, COL2 CHAR(15), COL3 DATE, COL4 CHAR(15), COL5 DATE
CONSTRAINT PK PRIMARY KEY ( TETNANT_ID, PREFIX ) ) MULTI_TENANT=true;
CREATE VIEW IF NOT EXISTS DUMMY.GLOBAL_VIEW (PK1 DECIMAL(12, 3) NOT NULL, PK2
BIGINT NOT NULL, COL6 CHAR(15) , COL7 DATE, COL8 BOOLEAN, COL9 CHAR(15), COL10
VARCHAR, COL11 VARCHAR CONSTRAINT PKVIEW PRIMARY KEY (PK1 DESC, PK2)) AS SELECT
* FROM DUMMY.BASE WHERE PREFIX = '01A'; {code}
Tenant connection to create a view and repro the issue
{code:java}
0: jdbc:phoenix:localhost> CREATE VIEW DUMMY."0ph" AS SELECT * FROM
DUMMY.GLOBAL_VIEW;
No rows affected (0.055 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DUMMY."0ph" (PK1,PK2) VALUES (10.0,10);
1 row affected (0.038 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DUMMY."0ph" (PK1,PK2) VALUES (20.0,20);
1 row affected (0.008 seconds)
0: jdbc:phoenix:localhost> SELECT * FROM DUMMY."0ph";
++-+-+-+-+-+--+--+-+-+--+-+--+
| PREFIX | COL1 | COL2 | COL3
| COL4 | COL5 | PK1 |
PK2 | COL6 | COL7 |
COL8 | COL9 | COL |
++-+-+-+-+-+--+--+-+-+--+-+--+
| 01A | null | | null
| | null | 2E+1 | 20
| | null |
| | |
| 01A | null | | null
| | null | 1E+1 | 10
| | null |
| | |
++-+-+-+-+-+--+--+-+-+--+-+--+
2 rows selected (0.035 seconds)
0: jdbc:phoenix:localhost> DELETE FROM DUMMY."0ph" WHERE (PK1,PK2) IN
((10.0,10),(20.0,20));
No rows affected (0.024 seconds)
0: jdbc:phoenix:localhost> SELECT * FROM DUMMY."0ph";
++-+-+-+-+-+--+--+-+-+--+-+--+
| PREFIX | COL1 | COL2 | COL3
| COL4 | COL5 | PK1 |
PK2 | COL6 | COL7 |
COL8 | COL9 | COL |
++-+-+-+-+-+--+--+-+-+--+-+--+
| 01A | null | | null
| | null | 2E+1 | 20
| | null |
| | |
| 01A | null | | null
| | null | 1E+1 | 10
| | null |
| | |
[jira] [Created] (PHOENIX-6662) Failed to delete rows when PK has one or more DESC column with IN clause
Xinyi Yan created PHOENIX-6662:
--
Summary: Failed to delete rows when PK has one or more DESC column
with IN clause
Key: PHOENIX-6662
URL: https://issues.apache.org/jira/browse/PHOENIX-6662
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.16.1
Reporter: Xinyi Yan
{code:java}
0: jdbc:phoenix:localhost> CREATE TABLE DUMMY_THREE_PKS (PK1 VARCHAR(15), PK2
DOUBLE(10,3) NOT NULL, PK3 BIGINT NOT NULL CONSTRAINT PK PRIMARY KEY (PK1, PK2
DESC,PK3));
No rows affected (1.309 seconds)
0: jdbc:phoenix:localhost>
0: jdbc:phoenix:localhost> UPSERT INTO DUMMY_THREE_PKS VALUES
('00D',10.0,10);
1 row affected (0.033 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DUMMY_THREE_PKS VALUES
('00D',20.0,20);
1 row affected (0.003 seconds)
0: jdbc:phoenix:localhost>
0: jdbc:phoenix:localhost>
0: jdbc:phoenix:localhost> SELECT * FROM DUMMY_THREE_PKS;
+-+--+--+
| PK1 | PK2 |
PK3 |
+-+--+--+
| 00D | 20.0 | 20
|
| 00D | 10.0 | 10
|
+-+--+--+
2 rows selected (0.027 seconds)
0: jdbc:phoenix:localhost> DELETE FROM DUMMY_THREE_PKS WHERE (PK1,PK2) IN
(('00D',10.0,10),('00D',20.0,20));
No rows affected (0.013 seconds)
0: jdbc:phoenix:localhost> SELECT * FROM DUMMY_THREE_PKS;
+-+--+--+
| PK1 | PK2 |
PK3 |
+-+--+--+
| 00D | 20.0 | 20
|
| 00D | 10.0 | 10
|
+-+--+--+
2 rows selected (0.012 seconds)
0: jdbc:phoenix:localhost> EXPLAIN DELETE FROM DUMMY_THREE_PKS WHERE (PK1,PK2)
IN (('00D',10.0,10),('00D',20.0,20));
+--+--+--+--+
| PLAN | EST_BYTES_READ
| EST_ROWS_READ | EST_INFO_TS
|
+--+--+--+--+
| DELETE ROWS SERVER SELECT | null
| null | null
|
| CLIENT 1-CHUNK PARALLEL 1-WAY SKIP SCAN ON 2 KEYS OVER DUMMY_THREE_PKS
['00D',~20.0] - ['00D',~10.0] | null
| null |
| SERVER FILTER BY FIRST KEY ONLY AND (PK1, PK2) IN
([48,48,68,88,88,88,88,88,88,88,88,88,88,88,88,0,63,203,255,255,255,255,255,254,128,0,0,20],[48,48,68,88,88,88,88,88,88,88,88,88,88,88,88,0,63,
|
+--+--+--+--+
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (PHOENIX-6662) Failed to delete rows when PK has one or more DESC column with IN clause
[
https://issues.apache.org/jira/browse/PHOENIX-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6662:
---
Priority: Critical (was: Major)
> Failed to delete rows when PK has one or more DESC column with IN clause
>
>
> Key: PHOENIX-6662
> URL: https://issues.apache.org/jira/browse/PHOENIX-6662
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Priority: Critical
>
> {code:java}
> 0: jdbc:phoenix:localhost> CREATE TABLE DUMMY_THREE_PKS (PK1 VARCHAR(15), PK2
> DOUBLE(10,3) NOT NULL, PK3 BIGINT NOT NULL CONSTRAINT PK PRIMARY KEY (PK1,
> PK2 DESC,PK3));
> No rows affected (1.309 seconds)
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> UPSERT INTO DUMMY_THREE_PKS VALUES
> ('00D',10.0,10);
> 1 row affected (0.033 seconds)
> 0: jdbc:phoenix:localhost> UPSERT INTO DUMMY_THREE_PKS VALUES
> ('00D',20.0,20);
> 1 row affected (0.003 seconds)
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost>
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY_THREE_PKS;
> +-+--+--+
> | PK1 | PK2 |
> PK3 |
> +-+--+--+
> | 00D | 20.0 | 20
> |
> | 00D | 10.0 | 10
> |
> +-+--+--+
> 2 rows selected (0.027 seconds)
> 0: jdbc:phoenix:localhost> DELETE FROM DUMMY_THREE_PKS WHERE (PK1,PK2) IN
> (('00D',10.0,10),('00D',20.0,20));
> No rows affected (0.013 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY_THREE_PKS;
> +-+--+--+
> | PK1 | PK2 |
> PK3 |
> +-+--+--+
> | 00D | 20.0 | 20
> |
> | 00D | 10.0 | 10
> |
> +-+--+--+
> 2 rows selected (0.012 seconds)
> 0: jdbc:phoenix:localhost> EXPLAIN DELETE FROM DUMMY_THREE_PKS WHERE
> (PK1,PK2) IN (('00D',10.0,10),('00D',20.0,20));
> +--+--+--+--+
> | PLAN | EST_BYTES_READ
> | EST_ROWS_READ |
> EST_INFO_TS |
> +--+--+--+--+
> | DELETE ROWS SERVER SELECT | null
> | null | null
> |
> | CLIENT 1-CHUNK PARALLEL 1-WAY SKIP SCAN ON 2 KEYS OVER DUMMY_THREE_PKS
> ['00D',~20.0] - ['00D',~10.0] | null
> | null |
> | SERVER FILTER BY FIRST KEY ONLY AND (PK1, PK2) IN
> ([48,48,68,88,88,88,88,88,88,88,88,88,88,88,88,0,63,203,255,255,255,255,255,254,128,0,0,20],[48,48,68,88,88,88,88,88,88,88,88,88,88,88,88,0,63,
> |
> +--+--+--+--+
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (PHOENIX-6659) RVC with AND clauses return incorrect result
[
https://issues.apache.org/jira/browse/PHOENIX-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan resolved PHOENIX-6659.
Resolution: Fixed
Thanks for the patch!
> RVC with AND clauses return incorrect result
>
>
> Key: PHOENIX-6659
> URL: https://issues.apache.org/jira/browse/PHOENIX-6659
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Assignee: Gokcen Iskender
>Priority: Critical
> Attachments: Screen Shot 2022-03-01 at 1.26.44 PM.png
>
>
> CREATE TABLE DUMMY (PK1 VARCHAR NOT NULL, PK2 BIGINT NOT NULL, PK3 BIGINT NOT
> NULL CONSTRAINT PK PRIMARY KEY (PK1,PK2,PK3));
> UPSERT INTO DUMMY VALUES ('a',0,1);
> UPSERT INTO DUMMY VALUES ('a',1,1);
> UPSERT INTO DUMMY VALUES ('a',2,1);
> UPSERT INTO DUMMY VALUES ('a',3,1);
> UPSERT INTO DUMMY VALUES ('a',3,2);
> UPSERT INTO DUMMY VALUES ('a',4,1);
>
> {code:java}
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK1,PK2,PK3) <= ('a',3,1);
> +--+--++
> | PK1 | PK2
> | PK3 |
> +--+--++
> +--+--++
> No rows selected (0.045 seconds)
> 0: jdbc:phoenix:localhost> explain SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK1,PK2,PK3) <= ('a',3,1);
> +--+--++
> | PLAN | EST_BYTES_READ
> | EST_ROWS_READ |
> +--+--++
> | CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['a',*] -
> ['a',-9187343239835811840] | null |
> | SERVER FILTER BY FIRST KEY ONLY | null
> | null |
> +--+--++
> 2 rows selected (0.012 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK2,PK3) <= (3,1);
> +--+--++
> | PK1 | PK2
> | PK3 |
> +--+--++
> | a | 0
> | 1 |
> | a | 1
> | 1 |
> | a | 2
> | 1 |
> | a | 3
> | 1 |
> +--+--++
> 4 rows selected (0.014 seconds)
> 0: jdbc:phoenix:localhost> EXPLAIN SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK2,PK3) <= (3,1);
> +--+--++
> | PLAN | EST_BYTES_READ
> | EST_ROWS_READ |
> +--+--++
> | CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['a',*] -
> ['a',3] | null |
> | SERVER FILTER BY FIRST KEY ONLY | null
> | null |
> +--+--++
> 2 rows selected (0.004 seconds) {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (PHOENIX-6659) RVC with AND clauses return incorrect result
[
https://issues.apache.org/jira/browse/PHOENIX-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan reassigned PHOENIX-6659:
--
Assignee: Gokcen Iskender
> RVC with AND clauses return incorrect result
>
>
> Key: PHOENIX-6659
> URL: https://issues.apache.org/jira/browse/PHOENIX-6659
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Assignee: Gokcen Iskender
>Priority: Critical
> Attachments: Screen Shot 2022-03-01 at 1.26.44 PM.png
>
>
> CREATE TABLE DUMMY (PK1 VARCHAR NOT NULL, PK2 BIGINT NOT NULL, PK3 BIGINT NOT
> NULL CONSTRAINT PK PRIMARY KEY (PK1,PK2,PK3));
> UPSERT INTO DUMMY VALUES ('a',0,1);
> UPSERT INTO DUMMY VALUES ('a',1,1);
> UPSERT INTO DUMMY VALUES ('a',2,1);
> UPSERT INTO DUMMY VALUES ('a',3,1);
> UPSERT INTO DUMMY VALUES ('a',3,2);
> UPSERT INTO DUMMY VALUES ('a',4,1);
>
> {code:java}
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK1,PK2,PK3) <= ('a',3,1);
> +--+--++
> | PK1 | PK2
> | PK3 |
> +--+--++
> +--+--++
> No rows selected (0.045 seconds)
> 0: jdbc:phoenix:localhost> explain SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK1,PK2,PK3) <= ('a',3,1);
> +--+--++
> | PLAN | EST_BYTES_READ
> | EST_ROWS_READ |
> +--+--++
> | CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['a',*] -
> ['a',-9187343239835811840] | null |
> | SERVER FILTER BY FIRST KEY ONLY | null
> | null |
> +--+--++
> 2 rows selected (0.012 seconds)
> 0: jdbc:phoenix:localhost> SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK2,PK3) <= (3,1);
> +--+--++
> | PK1 | PK2
> | PK3 |
> +--+--++
> | a | 0
> | 1 |
> | a | 1
> | 1 |
> | a | 2
> | 1 |
> | a | 3
> | 1 |
> +--+--++
> 4 rows selected (0.014 seconds)
> 0: jdbc:phoenix:localhost> EXPLAIN SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
> (PK2,PK3) <= (3,1);
> +--+--++
> | PLAN | EST_BYTES_READ
> | EST_ROWS_READ |
> +--+--++
> | CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['a',*] -
> ['a',3] | null |
> | SERVER FILTER BY FIRST KEY ONLY | null
> | null |
> +--+--++
> 2 rows selected (0.004 seconds) {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (PHOENIX-6659) RVC with AND clauses return incorrect result
[
https://issues.apache.org/jira/browse/PHOENIX-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6659:
---
Description:
CREATE TABLE DUMMY (PK1 VARCHAR NOT NULL, PK2 BIGINT NOT NULL, PK3 BIGINT NOT
NULL CONSTRAINT PK PRIMARY KEY (PK1,PK2,PK3));
UPSERT INTO DUMMY VALUES ('a',0,1);
UPSERT INTO DUMMY VALUES ('a',1,1);
UPSERT INTO DUMMY VALUES ('a',2,1);
UPSERT INTO DUMMY VALUES ('a',3,1);
UPSERT INTO DUMMY VALUES ('a',3,2);
UPSERT INTO DUMMY VALUES ('a',4,1);
{code:java}
0: jdbc:phoenix:localhost> SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
(PK1,PK2,PK3) <= ('a',3,1);
+--+--++
| PK1 | PK2
| PK3 |
+--+--++
+--+--++
No rows selected (0.045 seconds)
0: jdbc:phoenix:localhost> explain SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
(PK1,PK2,PK3) <= ('a',3,1);
+--+--++
| PLAN | EST_BYTES_READ
| EST_ROWS_READ |
+--+--++
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['a',*] -
['a',-9187343239835811840] | null |
| SERVER FILTER BY FIRST KEY ONLY | null
| null |
+--+--++
2 rows selected (0.012 seconds)
0: jdbc:phoenix:localhost> SELECT * FROM DUMMY WHERE (PK1 = 'a') AND (PK2,PK3)
<= (3,1);
+--+--++
| PK1 | PK2
| PK3 |
+--+--++
| a | 0
| 1 |
| a | 1
| 1 |
| a | 2
| 1 |
| a | 3
| 1 |
+--+--++
4 rows selected (0.014 seconds)
0: jdbc:phoenix:localhost> EXPLAIN SELECT * FROM DUMMY WHERE (PK1 = 'a') AND
(PK2,PK3) <= (3,1);
+--+--++
| PLAN | EST_BYTES_READ
| EST_ROWS_READ |
+--+--++
| CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER DUMMY ['a',*] -
['a',3] | null |
| SERVER FILTER BY FIRST KEY ONLY | null
| null |
+--+--++
2 rows selected (0.004 seconds) {code}
was:
CREATE TABLE DUMMY (PK1 VARCHAR NOT NULL, PK2 BIGINT NOT NULL, PK3 BIGINT NOT
NULL CONSTRAINT PK PRIMARY KEY (PK1,PK2,PK3));
UPSERT INTO DUMMY VALUES ('a',0,1);
UPSERT INTO DUMMY VALUES ('a',1,1);
UPSERT INTO DUMMY VALUES ('a',2,1);
UPSERT INTO DUMMY VALUES ('a',3,1);
UPSERT INTO DUMMY VALUES ('a',3,2);
UPSERT INTO DUMMY VALUES ('a',4,1);
SELECT * FROM DUMMY WHERE (PK1 = 'a') AND (PK1,PK2,PK3) <= ('a',3,1);
!Screen Shot 2022-03-01 at 1.26.44 PM.png!
> RVC with AND clauses return incorrect result
>
>
> Key: PHOENIX-6659
> URL: https://issues.apache.org/jira/browse/PHOENIX-6659
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Priority: Critical
> Attachments: Screen Shot 2022-03-01 at 1.26.44 PM.png
>
>
> CREATE TABLE DUMMY (PK1 VARCHAR NOT NULL, PK2 BIGINT NOT NULL, PK3 BIGINT NOT
>
[jira] [Created] (PHOENIX-6659) RVC with AND clauses return incorrect result
Xinyi Yan created PHOENIX-6659:
--
Summary: RVC with AND clauses return incorrect result
Key: PHOENIX-6659
URL: https://issues.apache.org/jira/browse/PHOENIX-6659
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.16.1
Reporter: Xinyi Yan
Attachments: Screen Shot 2022-03-01 at 1.26.44 PM.png
CREATE TABLE DUMMY (PK1 VARCHAR NOT NULL, PK2 BIGINT NOT NULL, PK3 BIGINT NOT
NULL CONSTRAINT PK PRIMARY KEY (PK1,PK2,PK3));
UPSERT INTO DUMMY VALUES ('a',0,1);
UPSERT INTO DUMMY VALUES ('a',1,1);
UPSERT INTO DUMMY VALUES ('a',2,1);
UPSERT INTO DUMMY VALUES ('a',3,1);
UPSERT INTO DUMMY VALUES ('a',3,2);
UPSERT INTO DUMMY VALUES ('a',4,1);
SELECT * FROM DUMMY WHERE (PK1 = 'a') AND (PK1,PK2,PK3) <= ('a',3,1);
!Screen Shot 2022-03-01 at 1.26.44 PM.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (PHOENIX-6634) PhoenixResultSet.next method closes the result set if the scanner returns null
[
https://issues.apache.org/jira/browse/PHOENIX-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan resolved PHOENIX-6634.
Resolution: Fixed
> PhoenixResultSet.next method closes the result set if the scanner returns null
> --
>
> Key: PHOENIX-6634
> URL: https://issues.apache.org/jira/browse/PHOENIX-6634
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 4.17.0, 4.16.2
>
>
>
> {code:java}
> public void test() throws Exception {
> String query = "SELECT a_string FROM " + tableName + " WHERE
> organization_id=? LIMIT 1";
> Properties props = PropertiesUtil.deepCopy(TEST_PROPERTIES);
> try(Connection conn = DriverManager.getConnection(getUrl(), props)) {
> PreparedStatement statement = conn.prepareStatement(query);
> statement.setString(1, tenantId);
> ResultSet rs = statement.executeQuery();
> while (rs.next()) {
> }
> assertFalse(rs.next()); // exception happens here
> }
> } {code}
>
>
> {code:java}
> java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed. at
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:615)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
> at
> org.apache.phoenix.jdbc.PhoenixResultSet.checkOpen(PhoenixResultSet.java:288)
> at
> org.apache.phoenix.jdbc.PhoenixResultSet.next(PhoenixResultSet.java:847)
> at org.apache.phoenix.end2end.QueryIT.test(QueryIT.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){code}
> Need to remove the unnecessary close inside the next method.
>
> https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixResultSet.java#L855
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (PHOENIX-6634) PhoenixResultSet.next method closes the result set if the scanner returns null
[
https://issues.apache.org/jira/browse/PHOENIX-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan reassigned PHOENIX-6634:
--
Assignee: Xinyi Yan
> PhoenixResultSet.next method closes the result set if the scanner returns null
> --
>
> Key: PHOENIX-6634
> URL: https://issues.apache.org/jira/browse/PHOENIX-6634
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.16.1
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 4.17.0, 4.16.2
>
>
>
> {code:java}
> public void test() throws Exception {
> String query = "SELECT a_string FROM " + tableName + " WHERE
> organization_id=? LIMIT 1";
> Properties props = PropertiesUtil.deepCopy(TEST_PROPERTIES);
> try(Connection conn = DriverManager.getConnection(getUrl(), props)) {
> PreparedStatement statement = conn.prepareStatement(query);
> statement.setString(1, tenantId);
> ResultSet rs = statement.executeQuery();
> while (rs.next()) {
> }
> assertFalse(rs.next()); // exception happens here
> }
> } {code}
>
>
> {code:java}
> java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed. at
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:615)
> at
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
> at
> org.apache.phoenix.jdbc.PhoenixResultSet.checkOpen(PhoenixResultSet.java:288)
> at
> org.apache.phoenix.jdbc.PhoenixResultSet.next(PhoenixResultSet.java:847)
> at org.apache.phoenix.end2end.QueryIT.test(QueryIT.java:184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){code}
> Need to remove the unnecessary close inside the next method.
>
> https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixResultSet.java#L855
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (PHOENIX-6634) PhoenixResultSet.next method closes the result set if the scanner returns null
Xinyi Yan created PHOENIX-6634:
--
Summary: PhoenixResultSet.next method closes the result set if the
scanner returns null
Key: PHOENIX-6634
URL: https://issues.apache.org/jira/browse/PHOENIX-6634
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.16.1
Reporter: Xinyi Yan
Fix For: 4.17.0, 4.16.2
{code:java}
public void test() throws Exception {
String query = "SELECT a_string FROM " + tableName + " WHERE
organization_id=? LIMIT 1";
Properties props = PropertiesUtil.deepCopy(TEST_PROPERTIES);
try(Connection conn = DriverManager.getConnection(getUrl(), props)) {
PreparedStatement statement = conn.prepareStatement(query);
statement.setString(1, tenantId);
ResultSet rs = statement.executeQuery();
while (rs.next()) {
}
assertFalse(rs.next()); // exception happens here
}
} {code}
{code:java}
java.sql.SQLException: ERROR 1101 (XCL01): ResultSet is closed. at
org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:615)
at
org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:217)
at
org.apache.phoenix.jdbc.PhoenixResultSet.checkOpen(PhoenixResultSet.java:288)
at org.apache.phoenix.jdbc.PhoenixResultSet.next(PhoenixResultSet.java:847)
at org.apache.phoenix.end2end.QueryIT.test(QueryIT.java:184)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){code}
Need to remove the unnecessary close inside the next method.
https://github.com/apache/phoenix/blob/4.x/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixResultSet.java#L855
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (PHOENIX-5838) Add Histograms for Table level Metrics.
[ https://issues.apache.org/jira/browse/PHOENIX-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-5838. Resolution: Implemented > Add Histograms for Table level Metrics. > > > Key: PHOENIX-5838 > URL: https://issues.apache.org/jira/browse/PHOENIX-5838 > Project: Phoenix > Issue Type: Sub-task >Reporter: vikas meka >Assignee: vikas meka >Priority: Major > Labels: metric-collector, metrics > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6572) Add Metrics for SystemCatalog Table
[ https://issues.apache.org/jira/browse/PHOENIX-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6572. Resolution: Implemented > Add Metrics for SystemCatalog Table > --- > > Key: PHOENIX-6572 > URL: https://issues.apache.org/jira/browse/PHOENIX-6572 > Project: Phoenix > Issue Type: Sub-task >Reporter: vikas meka >Assignee: Xinyi Yan >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6544) Adding metadata inconsistency metric
[ https://issues.apache.org/jira/browse/PHOENIX-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6544. Fix Version/s: 5.1.0 4.16.1 Resolution: Fixed > Adding metadata inconsistency metric > > > Key: PHOENIX-6544 > URL: https://issues.apache.org/jira/browse/PHOENIX-6544 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Minor > Fix For: 4.16.1, 5.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6544) Adding metadata inconsistency metric
Xinyi Yan created PHOENIX-6544: -- Summary: Adding metadata inconsistency metric Key: PHOENIX-6544 URL: https://issues.apache.org/jira/browse/PHOENIX-6544 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Assignee: Xinyi Yan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6472) In case of region inconsistency phoenix should stop gracefully
[ https://issues.apache.org/jira/browse/PHOENIX-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6472: --- Fix Version/s: 4.17.0 > In case of region inconsistency phoenix should stop gracefully > -- > > Key: PHOENIX-6472 > URL: https://issues.apache.org/jira/browse/PHOENIX-6472 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Neha Gupta >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.17.0 > > > When Phoenix fetches HRegionLocation data via hbase client, in case of region > overlap/inconsistencies it should throw an exception and stop gracefully > instead of getting stuck in an infinite loop and create millions of > HRegionLocation objects. Phoenix CQSI code for [getting > AllTableRegions|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L664] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6472) In case of region inconsistency phoenix should stop gracefully
[ https://issues.apache.org/jira/browse/PHOENIX-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6472. Resolution: Fixed > In case of region inconsistency phoenix should stop gracefully > -- > > Key: PHOENIX-6472 > URL: https://issues.apache.org/jira/browse/PHOENIX-6472 > Project: Phoenix > Issue Type: Bug >Reporter: Neha Gupta >Assignee: Xinyi Yan >Priority: Major > > When Phoenix fetches HRegionLocation data via hbase client, in case of region > overlap/inconsistencies it should throw an exception and stop gracefully > instead of getting stuck in an infinite loop and create millions of > HRegionLocation objects. Phoenix CQSI code for [getting > AllTableRegions|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L664] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6472) In case of region inconsistency phoenix should stop gracefully
[ https://issues.apache.org/jira/browse/PHOENIX-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6472: --- Affects Version/s: 4.17.0 > In case of region inconsistency phoenix should stop gracefully > -- > > Key: PHOENIX-6472 > URL: https://issues.apache.org/jira/browse/PHOENIX-6472 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.17.0 >Reporter: Neha Gupta >Assignee: Xinyi Yan >Priority: Major > > When Phoenix fetches HRegionLocation data via hbase client, in case of region > overlap/inconsistencies it should throw an exception and stop gracefully > instead of getting stuck in an infinite loop and create millions of > HRegionLocation objects. Phoenix CQSI code for [getting > AllTableRegions|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L664] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6472) In case of region inconsistency phoenix should stop gracefully
[ https://issues.apache.org/jira/browse/PHOENIX-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6472: --- Affects Version/s: (was: 4.17.0) 4.16.0 > In case of region inconsistency phoenix should stop gracefully > -- > > Key: PHOENIX-6472 > URL: https://issues.apache.org/jira/browse/PHOENIX-6472 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Neha Gupta >Assignee: Xinyi Yan >Priority: Major > > When Phoenix fetches HRegionLocation data via hbase client, in case of region > overlap/inconsistencies it should throw an exception and stop gracefully > instead of getting stuck in an infinite loop and create millions of > HRegionLocation objects. Phoenix CQSI code for [getting > AllTableRegions|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L664] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6472) In case of region inconsistency phoenix should stop gracefully
[ https://issues.apache.org/jira/browse/PHOENIX-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6472: -- Assignee: Xinyi Yan (was: Neha Gupta) > In case of region inconsistency phoenix should stop gracefully > -- > > Key: PHOENIX-6472 > URL: https://issues.apache.org/jira/browse/PHOENIX-6472 > Project: Phoenix > Issue Type: Bug >Reporter: Neha Gupta >Assignee: Xinyi Yan >Priority: Major > > When Phoenix fetches HRegionLocation data via hbase client, in case of region > overlap/inconsistencies it should throw an exception and stop gracefully > instead of getting stuck in an infinite loop and create millions of > HRegionLocation objects. Phoenix CQSI code for [getting > AllTableRegions|https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L664] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6432) Add support for additional load generators
[ https://issues.apache.org/jira/browse/PHOENIX-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6432. Resolution: Implemented > Add support for additional load generators > -- > > Key: PHOENIX-6432 > URL: https://issues.apache.org/jira/browse/PHOENIX-6432 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6432) Add support for additional load generators
[ https://issues.apache.org/jira/browse/PHOENIX-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6432: -- Assignee: Jacob Isaac > Add support for additional load generators > -- > > Key: PHOENIX-6432 > URL: https://issues.apache.org/jira/browse/PHOENIX-6432 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6435) Fix ViewTTLIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6435. Resolution: Fixed > Fix ViewTTLIT test flapper > -- > > Key: PHOENIX-6435 > URL: https://issues.apache.org/jira/browse/PHOENIX-6435 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Blocker > Fix For: 4.16.1, 4.17.0, 5.2.0 > > > [ERROR] Errors: > [ERROR] > PermissionNSDisabledWithCustomAccessControllerIT>BasePermissionsIT.testAutomaticGrantWithIndexAndView:1278->BasePermissionsIT.verifyAllowed:769->BasePermissionsIT.verifyAllowed:776 > ? UndeclaredThrowable > [ERROR] > PermissionNSEnabledWithCustomAccessControllerIT>BasePermissionsIT.testAutomaticGrantWithIndexAndView:1279->BasePermissionsIT.verifyAllowed:769->BasePermissionsIT.verifyAllowed:776 > ? UndeclaredThrowable > [ERROR] ImmutableIndexIT.testGlobalImmutableIndexDelete:407 ? StackOverflow > > mvn verify failed with the above error. We have to address and fix test > flappers before releasing the next 4.16.1RC. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6435) Fix ViewTTLIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6435: --- Summary: Fix ViewTTLIT test flapper (was: Fix test flapper ImmutableIndexIT, PermissionNSDisabledWithCustomAccessControllerIT and PermissionNSEnabledWithCustomAccessControllerIT) > Fix ViewTTLIT test flapper > -- > > Key: PHOENIX-6435 > URL: https://issues.apache.org/jira/browse/PHOENIX-6435 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Blocker > Fix For: 4.16.1, 4.17.0, 5.2.0 > > > [ERROR] Errors: > [ERROR] > PermissionNSDisabledWithCustomAccessControllerIT>BasePermissionsIT.testAutomaticGrantWithIndexAndView:1278->BasePermissionsIT.verifyAllowed:769->BasePermissionsIT.verifyAllowed:776 > ? UndeclaredThrowable > [ERROR] > PermissionNSEnabledWithCustomAccessControllerIT>BasePermissionsIT.testAutomaticGrantWithIndexAndView:1279->BasePermissionsIT.verifyAllowed:769->BasePermissionsIT.verifyAllowed:776 > ? UndeclaredThrowable > [ERROR] ImmutableIndexIT.testGlobalImmutableIndexDelete:407 ? StackOverflow > > mvn verify failed with the above error. We have to address and fix test > flappers before releasing the next 4.16.1RC. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6431) Add support for auto assigning pmfs
[ https://issues.apache.org/jira/browse/PHOENIX-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6431. Resolution: Fixed > Add support for auto assigning pmfs > --- > > Key: PHOENIX-6431 > URL: https://issues.apache.org/jira/browse/PHOENIX-6431 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > When defining a load profile it may be convenient to not specify the > probability distribution weights at all times -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6431) Add support for auto assigning pmfs
[ https://issues.apache.org/jira/browse/PHOENIX-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6431: -- Assignee: Jacob Isaac > Add support for auto assigning pmfs > --- > > Key: PHOENIX-6431 > URL: https://issues.apache.org/jira/browse/PHOENIX-6431 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > When defining a load profile it may be convenient to not specify the > probability distribution weights at all times -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6429) Add support for global connections and sequential data generators
[ https://issues.apache.org/jira/browse/PHOENIX-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6429: --- Fix Version/s: 5.2.0 4.17.0 > Add support for global connections and sequential data generators > - > > Key: PHOENIX-6429 > URL: https://issues.apache.org/jira/browse/PHOENIX-6429 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > Fix For: 4.17.0, 5.2.0 > > > We may at times want to upsert or query using global connections. > Also add additional sequential data generators in addition to INTEGER and > VARCHAR data types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6430) Add support for full row update for tables when no columns specfied in scenario
[ https://issues.apache.org/jira/browse/PHOENIX-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6430: --- Fix Version/s: 5.2.0 4.17.0 > Add support for full row update for tables when no columns specfied in > scenario > --- > > Key: PHOENIX-6430 > URL: https://issues.apache.org/jira/browse/PHOENIX-6430 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > Fix For: 4.17.0, 5.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6430) Add support for full row update for tables when no columns specfied in scenario
[ https://issues.apache.org/jira/browse/PHOENIX-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6430. Resolution: Fixed > Add support for full row update for tables when no columns specfied in > scenario > --- > > Key: PHOENIX-6430 > URL: https://issues.apache.org/jira/browse/PHOENIX-6430 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > Fix For: 4.17.0, 5.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6429) Add support for global connections and sequential data generators
[ https://issues.apache.org/jira/browse/PHOENIX-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6429. Assignee: Jacob Isaac Resolution: Fixed Thanks for the PR [~jisaac] > Add support for global connections and sequential data generators > - > > Key: PHOENIX-6429 > URL: https://issues.apache.org/jira/browse/PHOENIX-6429 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > > We may at times want to upsert or query using global connections. > Also add additional sequential data generators in addition to INTEGER and > VARCHAR data types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6430) Add support for full row update for tables when no columns specfied in scenario
[ https://issues.apache.org/jira/browse/PHOENIX-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6430: -- Assignee: Jacob Isaac > Add support for full row update for tables when no columns specfied in > scenario > --- > > Key: PHOENIX-6430 > URL: https://issues.apache.org/jira/browse/PHOENIX-6430 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6435) Fix test flapper ImmutableIndexIT, PermissionNSDisabledWithCustomAccessControllerIT and PermissionNSEnabledWithCustomAccessControllerIT
Xinyi Yan created PHOENIX-6435: -- Summary: Fix test flapper ImmutableIndexIT, PermissionNSDisabledWithCustomAccessControllerIT and PermissionNSEnabledWithCustomAccessControllerIT Key: PHOENIX-6435 URL: https://issues.apache.org/jira/browse/PHOENIX-6435 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 4.16.1, 4.17.0, 5.2.0 [ERROR] Errors: [ERROR] PermissionNSDisabledWithCustomAccessControllerIT>BasePermissionsIT.testAutomaticGrantWithIndexAndView:1278->BasePermissionsIT.verifyAllowed:769->BasePermissionsIT.verifyAllowed:776 ? UndeclaredThrowable [ERROR] PermissionNSEnabledWithCustomAccessControllerIT>BasePermissionsIT.testAutomaticGrantWithIndexAndView:1279->BasePermissionsIT.verifyAllowed:769->BasePermissionsIT.verifyAllowed:776 ? UndeclaredThrowable [ERROR] ImmutableIndexIT.testGlobalImmutableIndexDelete:407 ? StackOverflow mvn verify failed with the above error. We have to address and fix test flappers before releasing the next 4.16.1RC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6118) Multi Tenant Workloads using PHERF
[ https://issues.apache.org/jira/browse/PHOENIX-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6118. Resolution: Fixed Thanks for the PR! > Multi Tenant Workloads using PHERF > -- > > Key: PHOENIX-6118 > URL: https://issues.apache.org/jira/browse/PHOENIX-6118 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > Time Spent: 3h 50m > Remaining Estimate: 0h > > Features like PHOENIX_TTL and Splittable SYSCAT need to be tested for a large > number of tenant views. > In the absence of support for creating a large number of tenant views - Multi > leveled views dynamically and be able to query them in a generic framework, > the teams have to write custom logic to replay/run functional and perf > testing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6417) Fix PHERF ITs that are failing in the local builds
[ https://issues.apache.org/jira/browse/PHOENIX-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6417. Resolution: Fixed Thanks for the patch [~jisaac] > Fix PHERF ITs that are failing in the local builds > -- > > Key: PHOENIX-6417 > URL: https://issues.apache.org/jira/browse/PHOENIX-6417 > Project: Phoenix > Issue Type: Sub-task >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Minor > Fix For: 4.17.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6320) support hbase profile param at the release script
[ https://issues.apache.org/jira/browse/PHOENIX-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6320. Resolution: Invalid The old release process has been deprecated, close the PR and Jira. > support hbase profile param at the release script > - > > Key: PHOENIX-6320 > URL: https://issues.apache.org/jira/browse/PHOENIX-6320 > Project: Phoenix > Issue Type: New Feature >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > > After PHOENIX-6307, we have the ability to release multi-hbase profiles at > one branch, but we need to provide an option for each release run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6396) PChar illegal data exception should not contain value
[ https://issues.apache.org/jira/browse/PHOENIX-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6396: --- Fix Version/s: (was: 4.17.0) 4.16.1 > PChar illegal data exception should not contain value > - > > Key: PHOENIX-6396 > URL: https://issues.apache.org/jira/browse/PHOENIX-6396 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.1, 4.16.1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6386) Bulkload generates unverified index rows
[ https://issues.apache.org/jira/browse/PHOENIX-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6386: --- Fix Version/s: (was: 4.17.0) 4.16.1 > Bulkload generates unverified index rows > > > Key: PHOENIX-6386 > URL: https://issues.apache.org/jira/browse/PHOENIX-6386 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.1, 4.16.1, 5.2.0 > > > Bulkload sets the index status cell of the generated global index rows to the > default 'x' value. > As a result, all such indexes are treated as unverified, and the first access > will generate index verification load, and be very slow. > We should generate the index rows with the VERIFIED state. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6370) 4.x branch still includes the phoenix-pig example files
[ https://issues.apache.org/jira/browse/PHOENIX-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6370: --- Fix Version/s: (was: 4.17.0) 4.16.1 > 4.x branch still includes the phoenix-pig example files > --- > > Key: PHOENIX-6370 > URL: https://issues.apache.org/jira/browse/PHOENIX-6370 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Trivial > Fix For: 4.16.1 > > > remove them -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6399) Updating BackwardCompatibilityIT supported versions
[ https://issues.apache.org/jira/browse/PHOENIX-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6399: -- Assignee: Xinyi Yan > Updating BackwardCompatibilityIT supported versions > --- > > Key: PHOENIX-6399 > URL: https://issues.apache.org/jira/browse/PHOENIX-6399 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.17.0, 5.2.0 > > > After the 4.16/5.1 release, we should add/update BackwardCompatibilityIT for > supported client versions. This will allow us to catch any backward > compatibilities in advance. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6400) Local index query returns incorrect values with other columns in the WHERE clause
[
https://issues.apache.org/jira/browse/PHOENIX-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6400:
---
Fix Version/s: 4.16.1
> Local index query returns incorrect values with other columns in the WHERE
> clause
> -
>
> Key: PHOENIX-6400
> URL: https://issues.apache.org/jira/browse/PHOENIX-6400
> Project: Phoenix
> Issue Type: Bug
>Reporter: Lars Hofhansl
>Priority: Blocker
> Fix For: 5.1.1, 4.16.1
>
> Attachments: 6400-test-5.1.txt
>
>
> {code}
> > create table test(pk1 integer not null primary key, v1 float, v2 float, v3
> > float);
> > create local index L1 on test (v1);
> > upsert into test values(1000, 0.01, 0.1, 0.5);
> > select * from test where v1 < 0.1;
> +--+--+-+-+
> | PK1 | V1 | V2 | V3 |
> +--+--+-+-+
> | 1000 | 0.01 | 0.1 | 0.5 |
> +--+--+-+-+
> > select * from test where v1 < 0.1 and v2 < 10.0;
> +-++++
> | PK1 | V1 | V2 | V3 |
> +-++++
> > select /*+ NO_INDEX */ * from test where v1 < 0.1 and v2 < 10.0;
> +--+--+-+-+
> | PK1 | V1 | V2 | V3 |
> +--+--+-+-+
> | 1000 | 0.01 | 0.1 | 0.5 |
> +--+--+-+-+
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-6399) Updating BackwardCompatibilityIT supported versions
Xinyi Yan created PHOENIX-6399: -- Summary: Updating BackwardCompatibilityIT supported versions Key: PHOENIX-6399 URL: https://issues.apache.org/jira/browse/PHOENIX-6399 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Fix For: 4.17.0, 5.2.0 After the 4.16/5.1 release, we should add/update BackwardCompatibilityIT for supported client versions. This will allow us to catch any backward compatibilities in advance. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6399) Updating BackwardCompatibilityIT supported versions
[ https://issues.apache.org/jira/browse/PHOENIX-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6399: --- Issue Type: Test (was: Improvement) > Updating BackwardCompatibilityIT supported versions > --- > > Key: PHOENIX-6399 > URL: https://issues.apache.org/jira/browse/PHOENIX-6399 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Priority: Major > Fix For: 4.17.0, 5.2.0 > > > After the 4.16/5.1 release, we should add/update BackwardCompatibilityIT for > supported client versions. This will allow us to catch any backward > compatibilities in advance. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6388) Add sampled logging for read repairs
[ https://issues.apache.org/jira/browse/PHOENIX-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6388. Resolution: Fixed > Add sampled logging for read repairs > > > Key: PHOENIX-6388 > URL: https://issues.apache.org/jira/browse/PHOENIX-6388 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Minor > Fix For: 5.1.1, 4.16.1, 4.17.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6396) PChar illegal data exception should not contain value
[ https://issues.apache.org/jira/browse/PHOENIX-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6396. Resolution: Fixed > PChar illegal data exception should not contain value > - > > Key: PHOENIX-6396 > URL: https://issues.apache.org/jira/browse/PHOENIX-6396 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.1, 4.17.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6396) PChar illegal data exception should not contain value
Xinyi Yan created PHOENIX-6396: -- Summary: PChar illegal data exception should not contain value Key: PHOENIX-6396 URL: https://issues.apache.org/jira/browse/PHOENIX-6396 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 5.1.1, 4.17.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6388) Add sampled logging for read repairs
Xinyi Yan created PHOENIX-6388: -- Summary: Add sampled logging for read repairs Key: PHOENIX-6388 URL: https://issues.apache.org/jira/browse/PHOENIX-6388 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 5.1.1, 4.16.1, 4.17.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6343) Phoenix allows duplicate column names when one of them is a primary key
[
https://issues.apache.org/jira/browse/PHOENIX-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6343:
---
Fix Version/s: (was: 4.17.0)
4.16.0
> Phoenix allows duplicate column names when one of them is a primary key
> ---
>
> Key: PHOENIX-6343
> URL: https://issues.apache.org/jira/browse/PHOENIX-6343
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Istvan Toth
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 5.1.1, 4.16.0, 5.2.0
>
>
> {code:sql}
> CREATE TABLE IF NOT EXISTS test_duplicate_columns (
> name VARCHAR NOT NULL PRIMARY KEY,
> city VARCHAR, name VARCHAR);
> {code}
> {noformat}
> select * from test_duplicate_columns;
> +--+--+--+
> | NAME | CITY | NAME |
> +--+--+--+
> +--+--+--+
> No rows selected (0.015 seconds)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6344) CASCADE on ALTER should NOOP when there are no secondary indexes
[ https://issues.apache.org/jira/browse/PHOENIX-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6344: --- Fix Version/s: (was: 4.17.0) (was: 4.16.1) 4.16.0 > CASCADE on ALTER should NOOP when there are no secondary indexes > > > Key: PHOENIX-6344 > URL: https://issues.apache.org/jira/browse/PHOENIX-6344 > Project: Phoenix > Issue Type: Improvement >Reporter: Swaroopa Kadam >Assignee: Swaroopa Kadam >Priority: Minor > Fix For: 4.16.0, 5.2.0 > > > When a table/view does not have a secondary index, using cascade in the ALTER > TABLE/VIEW .. ADD should continue with default behavior (of only > adding the column to table/view like a regular alter statement) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6380) phoenix-client-embedded depends on logging classes
[ https://issues.apache.org/jira/browse/PHOENIX-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6380: --- Fix Version/s: (was: 4.17.0) 4.16.0 > phoenix-client-embedded depends on logging classes > -- > > Key: PHOENIX-6380 > URL: https://issues.apache.org/jira/browse/PHOENIX-6380 > Project: Phoenix > Issue Type: Improvement > Components: core >Affects Versions: core >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.1, 4.16.0, 5.2.0 > > > While we are excluding org.slf4j:slf4j-log4j12 from the embedded client, it > is added to to dependency list instead. > We should probably find a way not have those as a dependency. > One possibility is excluding it from the phoenix-core dependency. > We may also trun those into optional dependcies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6382) Shaded artifact names and descriptions have unresolved ${hbase.profile} strings
[
https://issues.apache.org/jira/browse/PHOENIX-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6382:
---
Fix Version/s: (was: 4.17.0)
4.16.0
> Shaded artifact names and descriptions have unresolved ${hbase.profile}
> strings
> ---
>
> Key: PHOENIX-6382
> URL: https://issues.apache.org/jira/browse/PHOENIX-6382
> Project: Phoenix
> Issue Type: Bug
> Components: core
>Affects Versions: 5.1.0, 4.16.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 5.1.1, 4.16.0, 5.2.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6379) Implement a new Metric Type which will be used for TableMetrics
[ https://issues.apache.org/jira/browse/PHOENIX-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6379. Resolution: Fixed Thanks for the patch [~vmeka] > Implement a new Metric Type which will be used for TableMetrics > --- > > Key: PHOENIX-6379 > URL: https://issues.apache.org/jira/browse/PHOENIX-6379 > Project: Phoenix > Issue Type: Sub-task >Reporter: vikas meka >Assignee: vikas meka >Priority: Major > Fix For: 4.17.0, 5.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6377) phoenix-client has erronous maven dependecies
[ https://issues.apache.org/jira/browse/PHOENIX-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6377: --- Fix Version/s: (was: 4.17.0) 4.16.0 > phoenix-client has erronous maven dependecies > - > > Key: PHOENIX-6377 > URL: https://issues.apache.org/jira/browse/PHOENIX-6377 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Critical > Fix For: 5.1.1, 4.16.0, 5.2.0 > > > depending on phoenix-client brings in phoenix-core, and all of its > dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6379) Implement a new Metric Type which will be used for TableMetrics
[ https://issues.apache.org/jira/browse/PHOENIX-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6379: --- Fix Version/s: 5.2.0 4.17.0 > Implement a new Metric Type which will be used for TableMetrics > --- > > Key: PHOENIX-6379 > URL: https://issues.apache.org/jira/browse/PHOENIX-6379 > Project: Phoenix > Issue Type: Sub-task >Reporter: vikas meka >Priority: Major > Fix For: 4.17.0, 5.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6360) phoenix-core has compile dependency on phoenix-hbase-compat
[ https://issues.apache.org/jira/browse/PHOENIX-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6360: --- Fix Version/s: (was: 4.17.0) 4.16.0 > phoenix-core has compile dependency on phoenix-hbase-compat > --- > > Key: PHOENIX-6360 > URL: https://issues.apache.org/jira/browse/PHOENIX-6360 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: 5.1.0, 4.16.0 >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Blocker > Fix For: 5.1.0, 4.16.0 > > > We are adding phoenix-hbase-compat-X.X.X to phoenix-core as a dependency. > phoenix-core is supposed to be hbase profile neutral, and the consumer shoudl > add their the phoenix-hbase-compat-X.X.X module manually. > This breaks, or requires ugly workarounds in consumers of phoenix-core, like > phoenix-connectors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6114) Create shaded phoenix-pherf and remove lib dir from assembly
[ https://issues.apache.org/jira/browse/PHOENIX-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6114: --- Fix Version/s: (was: 4.17.0) 4.16.0 > Create shaded phoenix-pherf and remove lib dir from assembly > > > Key: PHOENIX-6114 > URL: https://issues.apache.org/jira/browse/PHOENIX-6114 > Project: Phoenix > Issue Type: Improvement > Components: core >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > The Phoenix assembly has a poorly maintained lib directory, with dependencies > that we are for submodules that have since been moved to phoenix-queryserver. > The core phoenix jars are shaded, and do not or use the libraries here. > phoenix-tracing-webapp is not included in the assembly, and thus does not > need dependencies there. > That leaves phoenix-pherf as a possible consumer of these dependencies. > I propose building refactoring phoenix-pherf similarly to > phoenix-queryserver, as a mostly self-contained shaded JAR, that only depends > on phoenix-client, and has the rest of its dependencies shaded in. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6348) java.lang.NoClassDefFoundError: when running with hbase-1.6
[ https://issues.apache.org/jira/browse/PHOENIX-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6348: --- Fix Version/s: (was: 4.16.0) 4.17.0 4.16.1 > java.lang.NoClassDefFoundError: when running with hbase-1.6 > --- > > Key: PHOENIX-6348 > URL: https://issues.apache.org/jira/browse/PHOENIX-6348 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Jacob Isaac >Priority: Blocker > Fix For: 4.16.1, 4.17.0 > > > Getting this error, when running with hbase-1.6 > I think this stems from the jar dependency mismatch between phoenix 4.x/4.16 > and hbase1.6 > hbase-1.6 : commons-cli-1.2.jar > (https://github.com/apache/hbase/blob/5ec5a5b115ee36fb28903667c008218abd21b3f5/pom.xml#L1260) > phoenix 4.x : commons-cli-1.4.jar > ([https://github.com/apache/phoenix/blob/44d44029597d032af1be54d5e9a70342c1fe4769/pom.xml#L100)] > > What is the best way to resolve this? Shading? > [~stoty] [~vjasani] > FYI > [~yanxinyi] [~ChinmayKulkarni] [~kadir] > > **Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/cli/DefaultParser > at > org.apache.phoenix.mapreduce.index.IndexTool.parseOptions(IndexTool.java:354) > at org.apache.phoenix.mapreduce.index.IndexTool.run(IndexTool.java:788) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90) > at org.apache.phoenix.mapreduce.index.IndexTool.main(IndexTool.java:1201) > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.cli.DefaultParser > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5140) TableNotFoundException occurs when we create local asynchronous index
[
https://issues.apache.org/jira/browse/PHOENIX-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-5140:
---
Fix Version/s: (was: 4.16.0)
4.17.0
4.16.1
> TableNotFoundException occurs when we create local asynchronous index
> -
>
> Key: PHOENIX-5140
> URL: https://issues.apache.org/jira/browse/PHOENIX-5140
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 5.0.0
> Environment: > HDP : 3.0.0.0， HBase : 2.0.0，phoenix : 5.0.0 and
> hadoop : 3.1.0
>Reporter: MariaCarrie
>Assignee: dan zheng
>Priority: Major
> Labels: IndexTool, localIndex, tableUndefined
> Fix For: 5.1.0, 4.16.1, 4.17.0
>
> Attachments: PHOENIX-5140-master-v1.patch,
> PHOENIX-5140-master-v2.patch
>
> Original Estimate: 48h
> Time Spent: 20m
> Remaining Estimate: 47h 40m
>
> First I create the table and insert the data:
> ^create table DMP.DMP_INDEX_TEST2 (id varchar not null primary key,name
> varchar,age varchar);^
> ^upsert into DMP.DMP_INDEX_TEST2 values('id01','name01','age01');^
> The asynchronous index is then created:
> ^create local index if not exists TMP_INDEX_DMP_TEST2 on DMP.DMP_INDEX_TEST2
> (name) ASYNC;^
> Because kerberos is enabled,So I need kinit HBase principal first,Then
> execute the following command:
> ^HADOOP_CLASSPATH="/etc/hbase/conf" hadoop jar
> /usr/hdp/3.0.0.0-1634/phoenix/phoenix-client.jar
> org.apache.phoenix.mapreduce.index.IndexTool --schema DMP --data-table
> DMP_INDEX_TEST2 --index-table TMP_INDEX_DMP_TEST2 --output-path
> /hbase-backup2^
> But I got the following error:
> ^Error: java.lang.RuntimeException:
> org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table
> undefined. tableName=DMP.DMP_INDEX_TEST2^
> ^at
> org.apache.phoenix.mapreduce.index.PhoenixIndexImportMapper.map(PhoenixIndexImportMapper.java:124)^
> ^at
> org.apache.phoenix.mapreduce.index.PhoenixIndexImportMapper.map(PhoenixIndexImportMapper.java:50)^
> ^at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:146)^
> ^at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:799)^
> ^at org.apache.hadoop.mapred.MapTask.run(MapTask.java:347)^
> ^at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:174)^
> ^at java.security.AccessController.doPrivileged(Native Method)^
> ^at javax.security.auth.Subject.doAs(Subject.java:422)^
> ^at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)^
> ^at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:168)^
> ^Caused by: org.apache.phoenix.schema.TableNotFoundException: ERROR 1012
> (42M03): Table undefined. tableName=DMP.DMP_INDEX_TEST2^
> ^at
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getTableRegionLocation(ConnectionQueryServicesImpl.java:4544)^
> ^at
> org.apache.phoenix.query.DelegateConnectionQueryServices.getTableRegionLocation(DelegateConnectionQueryServices.java:312)^
> ^at
> org.apache.phoenix.compile.UpsertCompiler.setValues(UpsertCompiler.java:163)^
> ^at
> org.apache.phoenix.compile.UpsertCompiler.access$500(UpsertCompiler.java:118)^
> ^at
> org.apache.phoenix.compile.UpsertCompiler$UpsertValuesMutationPlan.execute(UpsertCompiler.java:1202)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:408)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:391)^
> ^at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:390)^
> ^at
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:378)^
> ^at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:173)^
> ^at
> org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(PhoenixPreparedStatement.java:183)^
> ^at
> org.apache.phoenix.mapreduce.index.PhoenixIndexImportMapper.map(PhoenixIndexImportMapper.java:103)^
> ^... 9 more^
> I can query this table and have access to it,It works well:
> ^select * from DMP.DMP_INDEX_TEST2;^
> ^select * from DMP.TMP_INDEX_DMP_TEST2;^
> ^drop table DMP.DMP_INDEX_TEST2;^
> But why did my MR task make this mistake? Any Suggestions from anyone?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5874) IndexTool does not set TTL on its log tables correctly
[ https://issues.apache.org/jira/browse/PHOENIX-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-5874: --- Fix Version/s: 5.1.1 > IndexTool does not set TTL on its log tables correctly > -- > > Key: PHOENIX-5874 > URL: https://issues.apache.org/jira/browse/PHOENIX-5874 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.14.3 >Reporter: Kadir OZDEMIR >Assignee: Swaroopa Kadam >Priority: Major > Fix For: 5.1.1, 4.16.0 > > Attachments: PHOENIX-5874.4.x.v1.patch, PHOENIX-5874.4.x.v2.patch > > Time Spent: 40m > Remaining Estimate: 0h > > IndexTool does not use the correct API to set 7 day TTL on its log tables. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6078) Remove Internal Phoenix Connections from parent LinkedQueue when closed
[ https://issues.apache.org/jira/browse/PHOENIX-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6078: --- Fix Version/s: (was: 4.17.0) > Remove Internal Phoenix Connections from parent LinkedQueue when closed > --- > > Key: PHOENIX-6078 > URL: https://issues.apache.org/jira/browse/PHOENIX-6078 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3, 4.x >Reporter: Saksham Gangwar >Assignee: Saksham Gangwar >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6078.4.x.patch, PHOENIX-6078.4.x.v2.patch, > PHOENIX-6078v2.4.x.patch, PHOENIX-6078v3.4.x.patch, PHOENIX-6078v4.4.x.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/PHOENIX-5872 > We started maintaining parent-child relationships between phoenix connections > to close those connections. But after closing those child connections we > should be removing them from the Queue which is being maintained for the same. > Here: > [https://github.com/apache/phoenix/blob/affa9e889efcc2ad7dac009a0d294b09447d281e/phoenix-core/src/main/java/org/apache/phoenix/compile/MutatingParallelIteratorFactory.java#L114] > > If not removed from the queue, and if the parent connection is being reused: > we are observing the OOM issue on the container side during the mapper run. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6182) IndexTool to verify and repair every index row
[ https://issues.apache.org/jira/browse/PHOENIX-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6182: -- Assignee: Tanuj Khurana (was: Xinyi Yan) > IndexTool to verify and repair every index row > -- > > Key: PHOENIX-6182 > URL: https://issues.apache.org/jira/browse/PHOENIX-6182 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Kadir OZDEMIR >Assignee: Tanuj Khurana >Priority: Major > Fix For: 4.16.0, 4.16.1 > > > IndexTool rebuilds and verifies every index row pointed by the data table. > However, IndexTool cannot clean up the index rows that are not referenced by > the data table if there are such index rows. In order to do that it needs to > scan index table regions and make sure that every index row is valid. For > example we can add an option called source table (as in IndexScrutinyTool) to > do repair and verify index rows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6182) IndexTool to verify and repair every index row
[ https://issues.apache.org/jira/browse/PHOENIX-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6182: -- Assignee: Xinyi Yan (was: Tanuj Khurana) > IndexTool to verify and repair every index row > -- > > Key: PHOENIX-6182 > URL: https://issues.apache.org/jira/browse/PHOENIX-6182 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 5.0.0, 4.15.0 >Reporter: Kadir OZDEMIR >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0, 4.16.1 > > > IndexTool rebuilds and verifies every index row pointed by the data table. > However, IndexTool cannot clean up the index rows that are not referenced by > the data table if there are such index rows. In order to do that it needs to > scan index table regions and make sure that every index row is valid. For > example we can add an option called source table (as in IndexScrutinyTool) to > do repair and verify index rows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6349) Add and use commons-cli to phoenix-thirdparty
[ https://issues.apache.org/jira/browse/PHOENIX-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6349: --- Fix Version/s: 4.16.0 5.1.0 > Add and use commons-cli to phoenix-thirdparty > - > > Key: PHOENIX-6349 > URL: https://issues.apache.org/jira/browse/PHOENIX-6349 > Project: Phoenix > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > We are hit hard by commons-cli bugs, and currently we msut stick to the > version used by HBase/Hadoop. > Adding commons-cli to phoenix-thirdparty would unchain us from the > Hbase/Hadoop version, and would let us add our own patches (modeled after > protobuf in HBase) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6336) Scan filter is incorrectly set to null for index rebuilds
[ https://issues.apache.org/jira/browse/PHOENIX-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6336: --- Affects Version/s: 5.1.0 > Scan filter is incorrectly set to null for index rebuilds > - > > Key: PHOENIX-6336 > URL: https://issues.apache.org/jira/browse/PHOENIX-6336 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.1.0, 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6250) Fix ViewMetadataIT test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan resolved PHOENIX-6250.
Resolution: Fixed
> Fix ViewMetadataIT test flapper
> ---
>
> Key: PHOENIX-6250
> URL: https://issues.apache.org/jira/browse/PHOENIX-6250
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6250.4.x.v3.patch, PHOENIX-6250.master.v3.patch
>
>
> ViewMetadataIT failed multi-times at 4.x branch.
> Here is the logging:
> {code:java}
> 17:32:58 [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 353.71 s <<< FAILURE! - in org.apache.phoenix.end2end.ViewMetadataIT
> 17:32:58 [ERROR]
> testRepeatedCreateAndDropCascadeTableWorks(org.apache.phoenix.end2end.ViewMetadataIT)
> Time elapsed: 11.52 s <<< FAILURE!
> 17:32:58 java.lang.AssertionError: View SCHEMA2.N74 should have been
> deleted when parent was dropped
> 17:32:58 at org.junit.Assert.fail(Assert.java:89)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.validateViewDoesNotExist(ViewMetadataIT.java:1373)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.testRepeatedCreateAndDropCascadeTableWorks(ViewMetadataIT.java:818)
> 17:32:58 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 17:32:58 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 17:32:58 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 17:32:58 at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6336) Scan filter is incorrectly set to null for index rebuilds
[ https://issues.apache.org/jira/browse/PHOENIX-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6336: --- Fix Version/s: 4.16.0 5.1.0 > Scan filter is incorrectly set to null for index rebuilds > - > > Key: PHOENIX-6336 > URL: https://issues.apache.org/jira/browse/PHOENIX-6336 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Minor > Fix For: 5.1.0, 4.16.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (PHOENIX-6250) Fix ViewMetadataIT test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan reopened PHOENIX-6250:
reopen this Jira since we see this test failed at 4.x and 4.16 branch.
{code:java}
Error MessageERROR 1012 (42M03): Table undefined.
tableName=SCHEMA2.SCHEMA1.N64Stacktraceorg.apache.phoenix.schema.TableNotFoundException:
ERROR 1012 (42M03): Table undefined. tableName=SCHEMA2.SCHEMA1.N64
at
org.apache.phoenix.schema.MetaDataClient.addColumnsAndIndexesFromAncestors(MetaDataClient.java:903)
at
org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4890)
at
org.apache.phoenix.schema.MetaDataClient.addTableToCache(MetaDataClient.java:4886)
at
org.apache.phoenix.schema.MetaDataClient.handleCreateTableMutationCode(MetaDataClient.java:3245)
at
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:3071)
at
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1105)
at
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:421)
at
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:413)
at
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:395)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:394)
at
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:382)
at
org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1884)
at
org.apache.phoenix.end2end.ViewMetadataIT.testRecreateViewWhoseParentWasDropped(ViewMetadataIT.java:802)
{code}
{code:java}
Error MessageView SCHEMA2.N76 should have been deleted when parent was
droppedStacktracejava.lang.AssertionError: View SCHEMA2.N76 should have
been deleted when parent was dropped
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.end2end.ViewMetadataIT.validateViewDoesNotExist(ViewMetadataIT.java:1375)
at
org.apache.phoenix.end2end.ViewMetadataIT.testViewAndTableAndDropCascade(ViewMetadataIT.java:1016)
{code}
{code:java}
Error MessageView SCHEMA3.N77 should have been deleted when parent was
droppedStacktracejava.lang.AssertionError: View SCHEMA3.N77 should have
been deleted when parent was dropped at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.end2end.ViewMetadataIT.validateViewDoesNotExist(ViewMetadataIT.java:1375)
at
org.apache.phoenix.end2end.ViewMetadataIT.testViewAndTableAndDropCascade(ViewMetadataIT.java:1017)
{code}
> Fix ViewMetadataIT test flapper
> ---
>
> Key: PHOENIX-6250
> URL: https://issues.apache.org/jira/browse/PHOENIX-6250
> Project: Phoenix
> Issue Type: Improvement
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6250.4.x.v3.patch, PHOENIX-6250.master.v3.patch
>
>
> ViewMetadataIT failed multi-times at 4.x branch.
> Here is the logging:
> {code:java}
> 17:32:58 [ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 0, Time
> elapsed: 353.71 s <<< FAILURE! - in org.apache.phoenix.end2end.ViewMetadataIT
> 17:32:58 [ERROR]
> testRepeatedCreateAndDropCascadeTableWorks(org.apache.phoenix.end2end.ViewMetadataIT)
> Time elapsed: 11.52 s <<< FAILURE!
> 17:32:58 java.lang.AssertionError: View SCHEMA2.N74 should have been
> deleted when parent was dropped
> 17:32:58 at org.junit.Assert.fail(Assert.java:89)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.validateViewDoesNotExist(ViewMetadataIT.java:1373)
> 17:32:58 at
> org.apache.phoenix.end2end.ViewMetadataIT.testRepeatedCreateAndDropCascadeTableWorks(ViewMetadataIT.java:818)
> 17:32:58 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 17:32:58 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 17:32:58 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 17:32:58 at java.lang.reflect.Method.invoke(Method.java:498)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-6320) support hbase profile param at the release script
Xinyi Yan created PHOENIX-6320: -- Summary: support hbase profile param at the release script Key: PHOENIX-6320 URL: https://issues.apache.org/jira/browse/PHOENIX-6320 Project: Phoenix Issue Type: New Feature Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 5.1.0, 4.16.0 After PHOENIX-6307, we have the ability to release multi-hbase profiles at one branch, but we need to provide an option for each release run. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6319) remove cp python logic from the release script
[ https://issues.apache.org/jira/browse/PHOENIX-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6319. Resolution: Fixed > remove cp python logic from the release script > -- > > Key: PHOENIX-6319 > URL: https://issues.apache.org/jira/browse/PHOENIX-6319 > Project: Phoenix > Issue Type: Bug >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0, 5.10 > > > After PHOENIX-5822, we no longer need cp python folder logic from the phoenix > release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6319) remove cp python logic from the release script
Xinyi Yan created PHOENIX-6319: -- Summary: remove cp python logic from the release script Key: PHOENIX-6319 URL: https://issues.apache.org/jira/browse/PHOENIX-6319 Project: Phoenix Issue Type: Bug Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 4.16.0, 5.10 After PHOENIX-5822, we no longer need cp python folder logic from the phoenix release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6311) Using phoenix-level table exists check in ViewUtil.getSystemTableForChildLinks
[ https://issues.apache.org/jira/browse/PHOENIX-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6311. Resolution: Fixed > Using phoenix-level table exists check in ViewUtil.getSystemTableForChildLinks > -- > > Key: PHOENIX-6311 > URL: https://issues.apache.org/jira/browse/PHOENIX-6311 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6311.4.x.patch > > > We should check a phoenix level table exists check rather than an HBase level > check. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6311) Using phoenix-level table exists check in ViewUtil.getSystemTableForChildLinks
[ https://issues.apache.org/jira/browse/PHOENIX-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6311: --- Attachment: PHOENIX-6311.4.x.patch > Using phoenix-level table exists check in ViewUtil.getSystemTableForChildLinks > -- > > Key: PHOENIX-6311 > URL: https://issues.apache.org/jira/browse/PHOENIX-6311 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6311.4.x.patch > > > We should check a phoenix level table exists check rather than an HBase level > check. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6311) Using phoenix-level table exists check in ViewUtil.getSystemTableForChildLinks
Xinyi Yan created PHOENIX-6311: -- Summary: Using phoenix-level table exists check in ViewUtil.getSystemTableForChildLinks Key: PHOENIX-6311 URL: https://issues.apache.org/jira/browse/PHOENIX-6311 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 5.1.0, 4.16.0 We should check a phoenix level table exists check rather than an HBase level check. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6257) Fix PartialIndexRebuilderIT test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6257. Resolution: Duplicate > Fix PartialIndexRebuilderIT test flapper > > > Key: PHOENIX-6257 > URL: https://issues.apache.org/jira/browse/PHOENIX-6257 > Project: Phoenix > Issue Type: Improvement >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > > PartialIndexRebuilderIT failed 2 out of last 10 runs. > > h3. Error Message > expected:<3> but was:<2> > h3. Stacktrace > java.lang.AssertionError: expected:<3> but was:<2> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.junit.Assert.assertEquals(Assert.java:633) at > org.apache.phoenix.end2end.index.PartialIndexRebuilderIT.testIndexWriteFailureDuringRebuild(PartialIndexRebuilderIT.java:895) > at > org.apache.phoenix.end2end.index.PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex(PartialIndexRebuilderIT.java:818) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.junit.runners.Suite.runChild(Suite.java:128) at > org.junit.runners.Suite.runChild(Suite.java:27) at > org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at > org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at > org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at > org.junit.runners.ParentRunner.run(ParentRunner.java:413) at > org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6302) Fix ConcurrentUpsertsWithoutIndexedColsIT flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan resolved PHOENIX-6302.
Resolution: Fixed
Thanks for the patch [~vjasani]!
> Fix ConcurrentUpsertsWithoutIndexedColsIT flapper
> -
>
> Key: PHOENIX-6302
> URL: https://issues.apache.org/jira/browse/PHOENIX-6302
> Project: Phoenix
> Issue Type: Test
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> ConcurrentUpsertsWithoutIndexedColsIT.testConcurrentUpsertsWithoutIndexedColumns
> is failing some times.
> Logs:
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.phoenix.end2end.ConcurrentMutationsExtendedIT.verifyIndexTable(ConcurrentMutationsExtendedIT.java:95)
> {code}
> e.g
> [build|https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/176/testReport/org.apache.phoenix.end2end/ConcurrentUpsertsWithoutIndexedColsIT/MatrixBuild___Matrix___HBASE_PROFILE2_2BuildAndTest___testConcurrentUpsertsWithoutIndexedColumns/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6297:
---
Attachment: PHOENIX-6297.master.v3.patch
> Fix IndexMetadataIT.testAsyncRebuildAll test flapper
>
>
> Key: PHOENIX-6297
> URL: https://issues.apache.org/jira/browse/PHOENIX-6297
> Project: Phoenix
> Issue Type: Test
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6297.4.x.patch, PHOENIX-6297.4.x.v3.patch,
> PHOENIX-6297.master.patch, PHOENIX-6297.master.v3.patch
>
>
> Based on the Jenkins log, we need to fix it before the 4.16 release.
> {code:java}
> Error Messageexpected:<[COMPLE]TED> but
> was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
> but was:<[STAR]TED>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
> {code}
>
> {code:java}
> Error MessageRan out of time waiting for index state to become ACTIVE last
> seen actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of
> time waiting for index state to become ACTIVE last seen actual state is
> BUILDING
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6297:
---
Attachment: PHOENIX-6297.4.x.v3.patch
> Fix IndexMetadataIT.testAsyncRebuildAll test flapper
>
>
> Key: PHOENIX-6297
> URL: https://issues.apache.org/jira/browse/PHOENIX-6297
> Project: Phoenix
> Issue Type: Test
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6297.4.x.patch, PHOENIX-6297.4.x.v3.patch,
> PHOENIX-6297.master.patch
>
>
> Based on the Jenkins log, we need to fix it before the 4.16 release.
> {code:java}
> Error Messageexpected:<[COMPLE]TED> but
> was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
> but was:<[STAR]TED>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
> {code}
>
> {code:java}
> Error MessageRan out of time waiting for index state to become ACTIVE last
> seen actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of
> time waiting for index state to become ACTIVE last seen actual state is
> BUILDING
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6301) Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6301: --- Fix Version/s: 5.1.0 > Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test > flapper > > > Key: PHOENIX-6301 > URL: https://issues.apache.org/jira/browse/PHOENIX-6301 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-6301.4.x.patch, PHOENIX-6301.4.x.v2.patch > > > h3. Error Message > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> > h3. Stacktrace > java.lang.AssertionError: > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:120) at > org.junit.Assert.assertEquals(Assert.java:146) at > org.apache.phoenix.end2end.BackwardCompatibilityTestUtil.assertExpectedOutput(BackwardCompatibilityTestUtil.java:272) > at > org.apache.phoenix.end2end.BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild(BackwardCompatibilityIT.java:376) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6301) Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6301: --- Attachment: PHOENIX-6301.4.x.v2.patch > Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test > flapper > > > Key: PHOENIX-6301 > URL: https://issues.apache.org/jira/browse/PHOENIX-6301 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6301.4.x.patch, PHOENIX-6301.4.x.v2.patch > > > h3. Error Message > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> > h3. Stacktrace > java.lang.AssertionError: > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:120) at > org.junit.Assert.assertEquals(Assert.java:146) at > org.apache.phoenix.end2end.BackwardCompatibilityTestUtil.assertExpectedOutput(BackwardCompatibilityTestUtil.java:272) > at > org.apache.phoenix.end2end.BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild(BackwardCompatibilityIT.java:376) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6301) Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6301: --- Attachment: PHOENIX-6301.4.x.patch > Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test > flapper > > > Key: PHOENIX-6301 > URL: https://issues.apache.org/jira/browse/PHOENIX-6301 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6301.4.x.patch > > > h3. Error Message > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> > h3. Stacktrace > java.lang.AssertionError: > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:120) at > org.junit.Assert.assertEquals(Assert.java:146) at > org.apache.phoenix.end2end.BackwardCompatibilityTestUtil.assertExpectedOutput(BackwardCompatibilityTestUtil.java:272) > at > org.apache.phoenix.end2end.BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild(BackwardCompatibilityIT.java:376) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6301) Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6301: -- Assignee: Xinyi Yan > Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test > flapper > > > Key: PHOENIX-6301 > URL: https://issues.apache.org/jira/browse/PHOENIX-6301 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > > h3. Error Message > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> > h3. Stacktrace > java.lang.AssertionError: > expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but > was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', > '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:120) at > org.junit.Assert.assertEquals(Assert.java:146) at > org.apache.phoenix.end2end.BackwardCompatibilityTestUtil.assertExpectedOutput(BackwardCompatibilityTestUtil.java:272) > at > org.apache.phoenix.end2end.BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild(BackwardCompatibilityIT.java:376) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6301) Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test flapper
Xinyi Yan created PHOENIX-6301: -- Summary: Fix BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild test flapper Key: PHOENIX-6301 URL: https://issues.apache.org/jira/browse/PHOENIX-6301 Project: Phoenix Issue Type: Test Reporter: Xinyi Yan Fix For: 4.16.0 h3. Error Message expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> h3. Stacktrace java.lang.AssertionError: expected:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', '2','TI','COMPLETED','4', 'K','V', 'key1','val2', 'key3','val3']> but was:<['TASK_TYPE','TABLE_NAME','TASK_STATUS','TASK_PRIORITY', '2','TI','STARTED','4', 'K','V', 'key1','val2', 'key3','val3']> at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.failNotEquals(Assert.java:835) at org.junit.Assert.assertEquals(Assert.java:120) at org.junit.Assert.assertEquals(Assert.java:146) at org.apache.phoenix.end2end.BackwardCompatibilityTestUtil.assertExpectedOutput(BackwardCompatibilityTestUtil.java:272) at org.apache.phoenix.end2end.BackwardCompatibilityIT.testSystemTaskCreationWithIndexAsyncRebuild(BackwardCompatibilityIT.java:376) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6297:
---
Description:
Based on the Jenkins log, we need to fix it before the 4.16 release.
{code:java}
Error Messageexpected:<[COMPLE]TED> but
was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
but was:<[STAR]TED>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at
org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
{code}
{code:java}
Error MessageRan out of time waiting for index state to become ACTIVE last seen
actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of time
waiting for index state to become ACTIVE last seen actual state is BUILDING
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
{code}
https://github.com/apache/phoenix/pull/1059
was:
Based on the Jenkins log, we need to fix it before the 4.16 release.
{code:java}
Error Messageexpected:<[COMPLE]TED> but
was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
but was:<[STAR]TED>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at
org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
{code}
{code:java}
Error MessageRan out of time waiting for index state to become ACTIVE last seen
actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of time
waiting for index state to become ACTIVE last seen actual state is BUILDING
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
{code}
> Fix IndexMetadataIT.testAsyncRebuildAll test flapper
>
>
> Key: PHOENIX-6297
> URL: https://issues.apache.org/jira/browse/PHOENIX-6297
> Project: Phoenix
> Issue Type: Test
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-6297.4.x.patch, PHOENIX-6297.master.patch
>
>
> Based on the Jenkins log, we need to fix it before the 4.16 release.
> {code:java}
> Error Messageexpected:<[COMPLE]TED> but
> was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
> but was:<[STAR]TED>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
> {code}
>
> {code:java}
> Error MessageRan out of time waiting for index state to become ACTIVE last
> seen actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of
> time waiting for index state to become ACTIVE last seen actual state is
> BUILDING
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
> {code}
>
>
>
> https://github.com/apache/phoenix/pull/1059
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6297:
---
Description:
Based on the Jenkins log, we need to fix it before the 4.16 release.
{code:java}
Error Messageexpected:<[COMPLE]TED> but
was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
but was:<[STAR]TED>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at
org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
{code}
{code:java}
Error MessageRan out of time waiting for index state to become ACTIVE last seen
actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of time
waiting for index state to become ACTIVE last seen actual state is BUILDING
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
{code}
was:
Based on the Jenkins log, we need to fix it before the 4.16 release.
{code:java}
Error Messageexpected:<[COMPLE]TED> but
was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
but was:<[STAR]TED>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at
org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
{code}
{code:java}
Error MessageRan out of time waiting for index state to become ACTIVE last seen
actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of time
waiting for index state to become ACTIVE last seen actual state is BUILDING
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
{code}
https://github.com/apache/phoenix/pull/1059
> Fix IndexMetadataIT.testAsyncRebuildAll test flapper
>
>
> Key: PHOENIX-6297
> URL: https://issues.apache.org/jira/browse/PHOENIX-6297
> Project: Phoenix
> Issue Type: Test
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-6297.4.x.patch, PHOENIX-6297.master.patch
>
>
> Based on the Jenkins log, we need to fix it before the 4.16 release.
> {code:java}
> Error Messageexpected:<[COMPLE]TED> but
> was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
> but was:<[STAR]TED>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
> {code}
>
> {code:java}
> Error MessageRan out of time waiting for index state to become ACTIVE last
> seen actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of
> time waiting for index state to become ACTIVE last seen actual state is
> BUILDING
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6300) Fix PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex test flapper
[ https://issues.apache.org/jira/browse/PHOENIX-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6300: --- Summary: Fix PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex test flapper (was: z) > Fix PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex test flapper > > > Key: PHOENIX-6300 > URL: https://issues.apache.org/jira/browse/PHOENIX-6300 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6300.4.x.patch > > > PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex failed 5 out of > last 10 runs. > > h3. Error Message > expected:<3> but was:<2> > h3. Stacktrace > java.lang.AssertionError: expected:<3> but was:<2> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.junit.Assert.assertEquals(Assert.java:633) at > org.apache.phoenix.end2end.index.PartialIndexRebuilderIT.testIndexWriteFailureDuringRebuild(PartialIndexRebuilderIT.java:895) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6300) Fix PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex test flapper
Xinyi Yan created PHOENIX-6300: -- Summary: Fix PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex test flapper Key: PHOENIX-6300 URL: https://issues.apache.org/jira/browse/PHOENIX-6300 Project: Phoenix Issue Type: Test Reporter: Xinyi Yan Assignee: Xinyi Yan Fix For: 4.16.0 PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex failed 5 out of last 10 runs. h3. Error Message expected:<3> but was:<2> h3. Stacktrace java.lang.AssertionError: expected:<3> but was:<2> at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.failNotEquals(Assert.java:835) at org.junit.Assert.assertEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:633) at org.apache.phoenix.end2end.index.PartialIndexRebuilderIT.testIndexWriteFailureDuringRebuild(PartialIndexRebuilderIT.java:895) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6300) z
[ https://issues.apache.org/jira/browse/PHOENIX-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6300: --- Summary: z (was: Fix PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex test flapper) > z > - > > Key: PHOENIX-6300 > URL: https://issues.apache.org/jira/browse/PHOENIX-6300 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > > PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex failed 5 out of > last 10 runs. > > h3. Error Message > expected:<3> but was:<2> > h3. Stacktrace > java.lang.AssertionError: expected:<3> but was:<2> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.junit.Assert.assertEquals(Assert.java:633) at > org.apache.phoenix.end2end.index.PartialIndexRebuilderIT.testIndexWriteFailureDuringRebuild(PartialIndexRebuilderIT.java:895) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6300) z
[ https://issues.apache.org/jira/browse/PHOENIX-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6300: --- Attachment: PHOENIX-6300.4.x.patch > z > - > > Key: PHOENIX-6300 > URL: https://issues.apache.org/jira/browse/PHOENIX-6300 > Project: Phoenix > Issue Type: Test >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-6300.4.x.patch > > > PartialIndexRebuilderIT.testIndexWriteFailureDisablingIndex failed 5 out of > last 10 runs. > > h3. Error Message > expected:<3> but was:<2> > h3. Stacktrace > java.lang.AssertionError: expected:<3> but was:<2> at > org.junit.Assert.fail(Assert.java:89) at > org.junit.Assert.failNotEquals(Assert.java:835) at > org.junit.Assert.assertEquals(Assert.java:647) at > org.junit.Assert.assertEquals(Assert.java:633) at > org.apache.phoenix.end2end.index.PartialIndexRebuilderIT.testIndexWriteFailureDuringRebuild(PartialIndexRebuilderIT.java:895) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6297:
---
Attachment: PHOENIX-6297.4.x.patch
> Fix IndexMetadataIT.testAsyncRebuildAll test flapper
>
>
> Key: PHOENIX-6297
> URL: https://issues.apache.org/jira/browse/PHOENIX-6297
> Project: Phoenix
> Issue Type: Test
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-6297.4.x.patch, PHOENIX-6297.master.patch
>
>
> Based on the Jenkins log, we need to fix it before the 4.16 release.
> {code:java}
> Error Messageexpected:<[COMPLE]TED> but
> was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
> but was:<[STAR]TED>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
> {code}
>
> {code:java}
> Error MessageRan out of time waiting for index state to become ACTIVE last
> seen actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of
> time waiting for index state to become ACTIVE last seen actual state is
> BUILDING
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
[
https://issues.apache.org/jira/browse/PHOENIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xinyi Yan updated PHOENIX-6297:
---
Attachment: PHOENIX-6297.master.patch
> Fix IndexMetadataIT.testAsyncRebuildAll test flapper
>
>
> Key: PHOENIX-6297
> URL: https://issues.apache.org/jira/browse/PHOENIX-6297
> Project: Phoenix
> Issue Type: Test
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Major
> Fix For: 4.16.0
>
> Attachments: PHOENIX-6297.master.patch
>
>
> Based on the Jenkins log, we need to fix it before the 4.16 release.
> {code:java}
> Error Messageexpected:<[COMPLE]TED> but
> was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
> but was:<[STAR]TED>
> at org.junit.Assert.assertEquals(Assert.java:117)
> at org.junit.Assert.assertEquals(Assert.java:146)
> at
> org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
> {code}
>
> {code:java}
> Error MessageRan out of time waiting for index state to become ACTIVE last
> seen actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of
> time waiting for index state to become ACTIVE last seen actual state is
> BUILDING
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
> at
> org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (PHOENIX-6297) Fix IndexMetadataIT.testAsyncRebuildAll test flapper
Xinyi Yan created PHOENIX-6297:
--
Summary: Fix IndexMetadataIT.testAsyncRebuildAll test flapper
Key: PHOENIX-6297
URL: https://issues.apache.org/jira/browse/PHOENIX-6297
Project: Phoenix
Issue Type: Test
Reporter: Xinyi Yan
Assignee: Xinyi Yan
Fix For: 4.16.0
Based on the Jenkins log, we need to fix it before the 4.16 release.
{code:java}
Error Messageexpected:<[COMPLE]TED> but
was:<[STAR]TED>Stacktraceorg.junit.ComparisonFailure: expected:<[COMPLE]TED>
but was:<[STAR]TED>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at
org.apache.phoenix.end2end.DropTableWithViewsIT.assertTaskColumns(DropTableWithViewsIT.java:184)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:691)
{code}
{code:java}
Error MessageRan out of time waiting for index state to become ACTIVE last seen
actual state is BUILDINGStacktracejava.lang.AssertionError: Ran out of time
waiting for index state to become ACTIVE last seen actual state is BUILDING
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.phoenix.util.TestUtil.waitForIndexState(TestUtil.java:1081)
at
org.apache.phoenix.end2end.index.IndexMetadataIT.testAsyncRebuildAll(IndexMetadataIT.java:688)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-6272) PHOENIX-5592 introduces Dummy.java without ASF license
[ https://issues.apache.org/jira/browse/PHOENIX-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan resolved PHOENIX-6272. Resolution: Duplicate Thanks for catching this [~stoty]. Made an addendum patch and applied it to the master branch. > PHOENIX-5592 introduces Dummy.java without ASF license > -- > > Key: PHOENIX-6272 > URL: https://issues.apache.org/jira/browse/PHOENIX-6272 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: master >Reporter: Istvan Toth >Assignee: Chao Wang >Priority: Major > > PHOENIX-5592 introduces a Dummy.java test file. > It contains a commented out stub that could perhaps be used as a template, > but more importantly it misses an ASF Header. > If this is was committed unintentionally, it should be removed, if it thought > to be useful as a template and kept, then at least the proper ASF license > header should be added. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5592) MapReduce job to asynchronously delete rows where the VIEW_TTL has expired.
[ https://issues.apache.org/jira/browse/PHOENIX-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-5592: --- Attachment: PHOENIX-5592.master.v3.patch > MapReduce job to asynchronously delete rows where the VIEW_TTL has expired. > --- > > Key: PHOENIX-5592 > URL: https://issues.apache.org/jira/browse/PHOENIX-5592 > Project: Phoenix > Issue Type: Sub-task >Reporter: Xinyi Yan >Assignee: Xinyi Yan >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5592.4.x.v4.patch, PHOENIX-5592.master.v3.patch, > PHOENIX-5592.master.v4.patch > > Time Spent: 7h > Remaining Estimate: 0h > > Find the entities from the system catalog which views have TTLs defined on > them. Spawn an MR job, whose splitter will create a map task. The mapper > issues “select count(1) from the entity and Inject TTL attributes and Delete > Hint during Map task. Since the current Phoniex MR framework doesn't support > this feature, PhoenixMultiViewReader, PhoenixMultiViewInputSplit, > PhoenixMultiViewInputFormat, and a few MR related util classes need to > implement. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-6272) PHOENIX-5592 introduces Dummy.java without ASF license
[ https://issues.apache.org/jira/browse/PHOENIX-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan reassigned PHOENIX-6272: -- Assignee: Xinyi Yan > PHOENIX-5592 introduces Dummy.java without ASF license > -- > > Key: PHOENIX-6272 > URL: https://issues.apache.org/jira/browse/PHOENIX-6272 > Project: Phoenix > Issue Type: Bug > Components: core >Affects Versions: master >Reporter: Istvan Toth >Assignee: Xinyi Yan >Priority: Major > > PHOENIX-5592 introduces a Dummy.java test file. > It contains a commented out stub that could perhaps be used as a template, > but more importantly it misses an ASF Header. > If this is was committed unintentionally, it should be removed, if it thought > to be useful as a template and kept, then at least the proper ASF license > header should be added. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-6270) Fix SystemTablesCreationOnConnectionIT.testUpgradeNotAllowed test failure on the master branch
Xinyi Yan created PHOENIX-6270: -- Summary: Fix SystemTablesCreationOnConnectionIT.testUpgradeNotAllowed test failure on the master branch Key: PHOENIX-6270 URL: https://issues.apache.org/jira/browse/PHOENIX-6270 Project: Phoenix Issue Type: Improvement Reporter: Xinyi Yan Fix For: 5.1.0 SystemTablesCreationOnConnectionIT.testUpgradeNotAllowed failed locally on the master branch but not the 4.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6266) When reading from index, ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7
[ https://issues.apache.org/jira/browse/PHOENIX-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6266: --- Priority: Critical (was: Major) > When reading from index, ERROR 201 (22000): Illegal data. Expected length of > at least 8 bytes, but had 7 > > > Key: PHOENIX-6266 > URL: https://issues.apache.org/jira/browse/PHOENIX-6266 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3 >Reporter: Gokcen Iskender >Assignee: Gokcen Iskender >Priority: Critical > Fix For: 5.1.0, 4.16.0 > > > If an index rowkey has a variable length column in it and ends with a fixed > column that happens to have the same byte as the separator byte at the end, > we trim that last byte thinking that it is a separator byte. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6266) When reading from index, ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7
[ https://issues.apache.org/jira/browse/PHOENIX-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6266: --- Fix Version/s: 4.16.0 5.1.0 > When reading from index, ERROR 201 (22000): Illegal data. Expected length of > at least 8 bytes, but had 7 > > > Key: PHOENIX-6266 > URL: https://issues.apache.org/jira/browse/PHOENIX-6266 > Project: Phoenix > Issue Type: Bug >Reporter: Gokcen Iskender >Assignee: Gokcen Iskender >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > If an index rowkey has a variable length column in it and ends with a fixed > column that happens to have the same byte as the separator byte at the end, > we trim that last byte thinking that it is a separator byte. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-6266) When reading from index, ERROR 201 (22000): Illegal data. Expected length of at least 8 bytes, but had 7
[ https://issues.apache.org/jira/browse/PHOENIX-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-6266: --- Affects Version/s: 4.14.3 > When reading from index, ERROR 201 (22000): Illegal data. Expected length of > at least 8 bytes, but had 7 > > > Key: PHOENIX-6266 > URL: https://issues.apache.org/jira/browse/PHOENIX-6266 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.14.3 >Reporter: Gokcen Iskender >Assignee: Gokcen Iskender >Priority: Major > Fix For: 5.1.0, 4.16.0 > > > If an index rowkey has a variable length column in it and ends with a fixed > column that happens to have the same byte as the separator byte at the end, > we trim that last byte thinking that it is a separator byte. -- This message was sent by Atlassian Jira (v8.3.4#803005)
