[jira] [Commented] (PHOENIX-2096) Tweak criteria for when round robin iterator is used

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

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

Hudson commented on PHOENIX-2096:
---------------------------------

FAILURE: Integrated in Phoenix-master #819 (See [https://builds.apache.org/job/Phoenix-master/819/])
PHOENIX-2096 Tweak criteria for when round robin iterator is used (jtaylor: rev 61f1900ddec5eb5c06245c999711e1fd0c67af53)
* phoenix-core/src/main/java/org/apache/phoenix/util/ScanUtil.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/ReverseScanIT.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java


> Tweak criteria for when round robin iterator is used
> ----------------------------------------------------
>
>                 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, PHOENIX-2096_v2.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 <yl...@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)