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

the choice of index by phoneix is not correct where do querying

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.1.0
    • 4.3.0, 3.3.0, 3.2.2, 4.2.2
    • None
    • None
    • phoenix4.1
      HBase 0.98.6
      hadoop 1.2.1

    Description

      1.create INDEX_TEST_TABLE:
      create table index_test_table (a varchar not null,b varchar not null,c varchar not null,d varchar,e varchar, f varchar constraint pk primary key(a,b,c));

      2.upsert some data into table.

      3.create index on 'D' and 'F'
      create index INDEX_TEST_TABLE_INDEX_D on INDEX_TEST_TABLE(A,D) include(B,C,E,F);
      5 rows affected (0.747 seconds)
      0: jdbc:phoenix:10.20.14.35:2181> create index INDEX_TEST_TABLE_INDEX_F on INDEX_TEST_TABLE(A,F) include(B,C,D,E);
      5 rows affected (0.748 seconds)

      4.query data on 'D'
      explain select * from INDEX_TEST_TABLE where A in ('1','2','3','4','5') and D in ('1111','2222','3333');

      5. it is ok:
      CLIENT PARALLEL 1-WAY SKIP SCAN ON 15 KEYS OVER INDEX_TEST_TABLE_INDEX_D ['1','1111'] - ['5','3333']

      6. but query data on 'F'
      explain select * from INDEX_TEST_TABLE where A in ('1','2','3','4','5') and F in ('1111','2222','3333');

      7. also use the index on 'D' and set filter on 'F'
      CLIENT PARALLEL 1-WAY SKIP SCAN ON 5 KEYS OVER INDEX_TEST_TABLE_INDEX_D ['1'] - ['5'] |
      SERVER FILTER BY F IN ('1111','2222','3333') |

      is this a bug in 4.1 version??

      Attachments

        1. PHOENIX-1346_addendum_v2.patch
          4 kB
          James R. Taylor
        2. PHOENIX-1436_addendum.patch
          2 kB
          rajeshbabu
        3. PHOENIX-1436_v2.patch
          3 kB
          James R. Taylor
        4. PHOENIX-1436.patch
          4 kB
          rajeshbabu

        Activity

          People

            rajesh23 rajeshbabu
            xufeng xufeng
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: