phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2096) Merge sort not being done when a scan is ordered by PK
Date Thu, 02 Jul 2015 17:49:05 GMT

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

Thomas D'Silva commented on PHOENIX-2096:
-----------------------------------------

+1 LGTM

> Merge sort not being done when a scan is ordered by PK
> ------------------------------------------------------
>
>                 Key: PHOENIX-2096
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2096
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>         Attachments: PHOENIX-2096.patch
>
>
> Date: Wed, 1 Jul 2015 14:34:24 -0700
> Subject: Re: Problem in finding the largest value of an indexed column
> From: Yufan Liu <yliu33@kent.edu>
> To: user@phoenix.apache.org
> When I made more tests, I find that this problem happens after table got split.
> Here is the DDL I use to create table and index:
> CREATE TABLE IF NOT EXISTS t1 (  
> uid BIGINT NOT NULL,  
> timestamp BIGINT NOT NULL, 
> eventName VARCHAR
> CONSTRAINT my_pk PRIMARY KEY (uid,  timestamp)) COMPRESSION='SNAPPY';
> CREATE INDEX timestamp_index ON t1 (timestamp) INCLUDE (eventName)
> Attach is the sample data I used for test. It has about 4000 rows, when the timestamp_index
table has one region, the query returns correct result: 1433334048443, but when I manually
split it into 4 regions (use hbase tool), it returns 1433333024961.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message