[PHOENIX-4322] DESC primary key column with variable length does not work in SkipScanFilter

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.11.0
• Fix Version/s: 4.14.0, 5.0.0
• Assignee: Wei Xue
• Reporter: Wei Xue
• Created: 25/Oct/17 22:02
• Updated: 08/Jun/19 03:40
• Resolved: 05/Dec/17 19:00

Description

Example:

    @Test
    public void inDescCompositePK3() throws Exception {
        String table = generateUniqueName();
        String ddl = "CREATE table " + table + " (oid VARCHAR NOT NULL, code VARCHAR NOT NULL constraint pk primary key (oid DESC, code DESC))";
        Object[][] insertedRows = new Object[][]{{"o1", "1"}, {"o2", "2"}, {"o3", "3"}};
        runQueryTest(ddl, upsert("oid", "code"), insertedRows, new Object[][]{{"o2", "2"}, {"o1", "1"}}, new WhereCondition("(oid, code)", "IN", "(('o2', '2'), ('o1', '1'))"),
            table);
    }

Here the last column in primary key is in DESC order and has variable length, and WHERE clause involves an "IN" operator with RowValueConstructor specifying all PK columns. We get no results.

This ends up being the root cause for not being able to use child/parent join optimization on DESC pk columns as described in PHOENIX-3050.

Issue Links

• blocks: PHOENIX-3050 Handle DESC columns in child/parent join optimization
• relates to: PHOENIX-5122 PHOENIX-4322 breaks client backward compatibility
• links to: GitHub Pull Request #278