phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4322) DESC primary key column with variable length does not work in SkipScanFilter
Date Wed, 25 Oct 2017 22:13:00 GMT

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

ASF GitHub Bot commented on PHOENIX-4322:
-----------------------------------------

GitHub user maryannxue opened a pull request:

    https://github.com/apache/phoenix/pull/278

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

    Changes:
    Avoid adding an extra trailing separator to the key

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/maryannxue/phoenix phoenix-4322

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/278.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #278
    
----

----


> 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
>
> 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
(v6.4.14#64029)

Mime
View raw message