[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.3.001.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.001.patch, PHOENIX-5704-4.x-HBase-1.3.patch, > PHOENIX-5704-master.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-master.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.001.patch, PHOENIX-5704-4.x-HBase-1.3.patch, > PHOENIX-5704-master.patch, PHOENIX-5704-master.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x-HBase-1.3.v2.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v3.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.3.v3.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v2.patch, > PHOENIX-5607.4.x-HBase-1.3.v3.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.3.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x-HBase-1.3.v2.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-master.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.patch, PHOENIX-5704-master.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.3.001.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.001.patch, > PHOENIX-5704-4.x-HBase-1.3.patch > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5707) Index rebuild after truncate incorrectly writes the included column value
Swaroopa Kadam created PHOENIX-5707:
---
Summary: Index rebuild after truncate incorrectly writes the
included column value
Key: PHOENIX-5707
URL: https://issues.apache.org/jira/browse/PHOENIX-5707
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.15.0
Reporter: Swaroopa Kadam
Assignee: Swaroopa Kadam
Fix For: 5.1.0, 4.15.1
{code:java}
@Test
public void testIncorrectRebuild() throws Exception {
String schemaName = generateUniqueName();
String dataTableName = generateUniqueName();
String dataTableFullName = SchemaUtil.getTableName(schemaName,
dataTableName);
String indexTableName = generateUniqueName();
String indexTableFullName = SchemaUtil.getTableName(schemaName,
indexTableName);
Properties props = PropertiesUtil.deepCopy(TEST_PROPERTIES);
try (Connection conn = DriverManager.getConnection(getUrl(), props)) {
conn.setAutoCommit(true);
conn.createStatement().execute("create table " + dataTableFullName +
" (id varchar(10) not null primary key, val1 varchar(10), val2
varchar(10), val3 varchar(10)) COLUMN_ENCODED_BYTES=0");
conn.createStatement().execute("CREATE INDEX " + indexTableName + " on
" +
dataTableFullName + " (val1) include (val2, val3)" );
//insert a full row
conn.createStatement().execute("upsert into " + dataTableFullName + "
values ('a', 'ab', 'efgh', 'abcd')");
Thread.sleep(1000);
// insert a partial row
conn.createStatement().execute("upsert into " + dataTableFullName + "
(id, val3) values ('a', 'uvwx')");
Thread.sleep(1000);
//insert a full row
conn.createStatement().execute("upsert into " + dataTableFullName + "
values ('a', 'ab', 'efgh', 'yuio')");
Thread.sleep(1000);
//insert a partial row
conn.createStatement().execute("upsert into " + dataTableFullName + "
(id, val3) values ('a', 'asdf')");
//truncate index table
ConnectionQueryServices queryServices =
conn.unwrap(PhoenixConnection.class).getQueryServices();
Admin admin = queryServices.getAdmin();
TableName tableName = TableName.valueOf(indexTableFullName);
admin.disableTable(tableName);
admin.truncateTable(tableName, false);
//rebuild index
runIndexTool(true, false, schemaName, dataTableName, indexTableName);
// we expect 2 versions to be written after rebuild, one for last full
row update and one for latest update
//assert
Scan scan = new Scan();
scan.setRaw(true);
scan.setMaxVersions(10);
HTable indexTable = new HTable(getUtility().getConfiguration(),
indexTableFullName);
HTable dataTable = new HTable(getUtility().getConfiguration(),
dataTableFullName);
long dataFullRowTS = 0;
ResultScanner rs = dataTable.getScanner(scan);
for (Result r : rs) {
for (Cell c : r.listCells()) {
String column = new String(CellUtil.cloneQualifier(c));
String value = new String(CellUtil.cloneValue(c));
if (column.equalsIgnoreCase("VAL3") &&
value.equalsIgnoreCase("yuio")) {
dataFullRowTS = c.getTimestamp();
}
}
}
rs = indexTable.getScanner(scan);
for (Result r : rs) {
for (Cell c : r.listCells()) {
long indexTS = c.getTimestamp();
String column = new String(CellUtil.cloneQualifier(c));
if (column.equalsIgnoreCase("0:VAL3") && indexTS ==
dataFullRowTS) {
String value = new String(CellUtil.cloneValue(c));
assertEquals("yuio", value); // if the ts is from full
rebuild row , value should also be from full rebuild row
}
}
}
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.3.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: (was: PHOENIX-5607.4.x-HBase-1.3.v2.patch) > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5629) Phoenix Function to Return HBase row timestamp
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-5629: --- Attachment: PHOENIX-5629.4.x-HBase-1.3.v1.patch > Phoenix Function to Return HBase row timestamp > -- > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Tanuj Khurana >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5629.4.x-HBase-1.3.v1.patch, > PHOENIX-5629.master.v1.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5629) Phoenix Function to Return HBase row timestamp
[ https://issues.apache.org/jira/browse/PHOENIX-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanuj Khurana updated PHOENIX-5629: --- Attachment: PHOENIX-5629.master.v1.patch > Phoenix Function to Return HBase row timestamp > -- > > Key: PHOENIX-5629 > URL: https://issues.apache.org/jira/browse/PHOENIX-5629 > Project: Phoenix > Issue Type: New Feature >Reporter: Geoffrey Jacoby >Assignee: Tanuj Khurana >Priority: Major > Fix For: 5.1.0, 4.16.0 > > Attachments: PHOENIX-5629.master.v1.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > t's occasionally useful when diagnosing an issue with Phoenix to be able to > easily look up the HBase timestamp of the HBase Cell returned by a Phoenix > query. > For example: > SELECT ROW_TIMESTAMP(Column1) FROM Table1 WHERE Column1 = 'SomeValue' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: (was: PHOENIX-5704-4.x-HBase-1.5.patch) > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5704) Covered column updates are not generated for previously deleted data table row
[ https://issues.apache.org/jira/browse/PHOENIX-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-5704: Attachment: PHOENIX-5704-4.x-HBase-1.3.patch > Covered column updates are not generated for previously deleted data table row > -- > > Key: PHOENIX-5704 > URL: https://issues.apache.org/jira/browse/PHOENIX-5704 > Project: Phoenix > Issue Type: Bug >Affects Versions: 5.0.0, 4.15.0, 4.14.3 >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan >Priority: Critical > Fix For: 5.1.0, 4.15.1, 4.14.4, 4.16.0 > > Attachments: PHOENIX-5704-4.x-HBase-1.3.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5705) SYSTEM.CATALOG rows are rewritten with high frequency
[
https://issues.apache.org/jira/browse/PHOENIX-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana reassigned PHOENIX-5705:
--
Assignee: Tanuj Khurana
> SYSTEM.CATALOG rows are rewritten with high frequency
> -
>
> Key: PHOENIX-5705
> URL: https://issues.apache.org/jira/browse/PHOENIX-5705
> Project: Phoenix
> Issue Type: Bug
>Affects Versions: 4.14.3
>Reporter: Priyank Porwal
>Assignee: Tanuj Khurana
>Priority: Major
> Fix For: 4.15.1, 4.14.4
>
>
> It seems every few ms, the following cells are being rewritten without any
> change in values - PENDING_DISABLE_COUNT,
> INDEX_STATE,INDEX_DISABLE_TIMESTAMP,ASYNC_REBUILD_TIMESTAMP,_0
> Sometimes the rewrites have the same cell timestamps as well.
> These cells are all relevant to secondary indexes to it is likely that
> automated index rebuild system or Phoenix MR job submitter has an issue. This
> is true even if the index state is Active 'a'.
>
> REPRO:
> scan 'SYSTEM.CATALOG',
> {LIMIT=>1,RAW=>true,VERSIONS=>10,STARTROW=>""
> Get syscatrowkey:
> SELECT ROWKEY_BYTES_STRING() FROM SYSTEM.CATALOG WHERE COLUMN_NAME IS NULL
> AND DATA_TABLE_NAME IS NOT NULL AND TABLE_NAME = ""
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.3.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch, PHOENIX-5607.4.x-HBase-1.3.v2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5607) Client-server backward compatibility tests
[ https://issues.apache.org/jira/browse/PHOENIX-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Guggilam updated PHOENIX-5607: -- Attachment: PHOENIX-5607.4.x-HBase-1.3.v2.patch > Client-server backward compatibility tests > --- > > Key: PHOENIX-5607 > URL: https://issues.apache.org/jira/browse/PHOENIX-5607 > Project: Phoenix > Issue Type: Test >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Sandeep Guggilam >Priority: Blocker > Labels: phoenix-hardening > Fix For: 4.16.0 > > Attachments: PHOENIX-5607.4.x-HBase-1.3.v1.patch, > PHOENIX-5607.4.x-HBase-1.3.v2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Filing this as a blocker for 4.16.0. > As we've seen with the various failed attempts to release 4.15.0 Phoenix' > backwards compatibility story is weak, and lacks tests - in fact there're no > tests. > We should not allow to ship 4.16.0 without improving that and without tests. > [~ckulkarni], [~gjacoby] , FYI, what we discussed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5706) IndexTool verification reports failure when data row has no covered column values
Kadir OZDEMIR created PHOENIX-5706: -- Summary: IndexTool verification reports failure when data row has no covered column values Key: PHOENIX-5706 URL: https://issues.apache.org/jira/browse/PHOENIX-5706 Project: Phoenix Issue Type: Bug Affects Versions: 4.14.3, 5.0.0 Reporter: Kadir OZDEMIR Assignee: Kadir OZDEMIR When the data row has no covered column, the IndexTool inline verification does not form the expect index row correctly. This was introduced by the previous patch for the inline verification (PHOENIX-5694). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5705) SYSTEM.CATALOG rows are rewritten with high frequency
Priyank Porwal created PHOENIX-5705:
---
Summary: SYSTEM.CATALOG rows are rewritten with high frequency
Key: PHOENIX-5705
URL: https://issues.apache.org/jira/browse/PHOENIX-5705
Project: Phoenix
Issue Type: Bug
Affects Versions: 4.14.3
Reporter: Priyank Porwal
Fix For: 4.15.1, 4.14.4
It seems every few ms, the following cells are being rewritten without any
change in values - PENDING_DISABLE_COUNT,
INDEX_STATE,INDEX_DISABLE_TIMESTAMP,ASYNC_REBUILD_TIMESTAMP,_0
Sometimes the rewrites have the same cell timestamps as well.
These cells are all relevant to secondary indexes to it is likely that
automated index rebuild system or Phoenix MR job submitter has an issue. This
is true even if the index state is Active 'a'.
REPRO:
scan 'SYSTEM.CATALOG',
{LIMIT=>1,RAW=>true,VERSIONS=>10,STARTROW=>""
Get syscatrowkey:
SELECT ROWKEY_BYTES_STRING() FROM SYSTEM.CATALOG WHERE COLUMN_NAME IS NULL AND
DATA_TABLE_NAME IS NOT NULL AND TABLE_NAME = ""
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5670) Add the neccesary Synchronisation to the tests in the PQS repo
[ https://issues.apache.org/jira/browse/PHOENIX-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5670. -- Fix Version/s: 5.1.0 Resolution: Fixed Merged. Thanks for the review [~elserj] > Add the neccesary Synchronisation to the tests in the PQS repo > -- > > Key: PHOENIX-5670 > URL: https://issues.apache.org/jira/browse/PHOENIX-5670 > Project: Phoenix > Issue Type: Bug >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We need to do add the same synchronisation that we added in PHOENIX-5554 for > the core repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
