Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-2096

Tweak criteria for when round robin iterator is used

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.5.0
    • Labels:

      Description

      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.

        Attachments

        1. PHOENIX-2096.patch
          4 kB
          James Taylor
        2. PHOENIX-2096_v2.patch
          6 kB
          James Taylor

          Activity

            People

            • Assignee:
              jamestaylor James Taylor
              Reporter:
              jamestaylor James Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: