phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kulkarni (Jira)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5944) Modify the PK of SYSTEM.TASK to avoid full table scans
Date Tue, 09 Jun 2020 00:26:00 GMT
Chinmay Kulkarni created PHOENIX-5944:
-----------------------------------------

             Summary: Modify the PK of SYSTEM.TASK to avoid full table scans
                 Key: PHOENIX-5944
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5944
             Project: Phoenix
          Issue Type: Improvement
    Affects Versions: 4.15.0
            Reporter: Chinmay Kulkarni
             Fix For: 5.1.0, 4.16.0


The PK of SYSTEM.TASK is (TASK_TYPE, TASK_TS, TENANT_ID, TABLE_SCHEM, TABLE_NAME) and the Task.queryTaskTable methods [1|https://github.com/apache/phoenix/blob/5f9364db7e4925229704706e148e62f4cf4ec4c2/phoenix-core/src/main/java/org/apache/phoenix/schema/task/Task.java#L181] and [2|https://github.com/apache/phoenix/blob/5f9364db7e4925229704706e148e62f4cf4ec4c2/phoenix-core/src/main/java/org/apache/phoenix/schema/task/Task.java#L226] do
a full table scan as mentioned.

Can we reorder/modify the PK to switch this to a range scan instead of a FTS? Let's discuss
if this is possible. Based on [PHOENIX-5943|https://issues.apache.org/jira/browse/PHOENIX-5943],
this change may be to either or both of SYSTEM.TASK_QUEUE and SYSTEM.TASK_HISTORY.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message