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

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786175#comment-16786175 ] 

Hudson commented on PHOENIX-4322:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #89 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/89/])
PHOENIX-5122: PHOENIX-4322 breaks client backward compatibility (chinmayskulkarni: rev 0780b8436d856c0778cff13f92c0f1f3de33af15)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/expression/RowValueConstructorExpression.java


> DESC primary key column with variable length does not work in SkipScanFilter
> ----------------------------------------------------------------------------
>
>                 Key: PHOENIX-4322
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4322
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.11.0
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>            Priority: Minor
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4322.patch
>
>
> Example:
> {code}
>     @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);
>     }
> {code}
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)