Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Mon, 27 Nov 2017 18:51:00 +0000 (UTC)
From: "James Taylor (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13112118.1508968948000.326325.1511808660329@Atlassian.JIRA>
In-Reply-To: <JIRA.13112118.1508968948000@Atlassian.JIRA>
References: <JIRA.13112118.1508968948000@Atlassian.JIRA> <JIRA.13112118.1508968948610@jira-lw-us.apache.org>
Subject: [jira] [Commented] (PHOENIX-4322) DESC primary key column with
 variable length does not work in SkipScanFilter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 27 Nov 2017 18:51:04 -0000


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

James Taylor commented on PHOENIX-4322:
---------------------------------------

Ping [~maryannxue]. Are you planning on pursuing this one? I think you need to look at the code that generates the row key for RVCs and prevent any trailing separators from being added.

> 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
>
>
> 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)