You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2021/05/21 16:30:00 UTC
[jira] [Updated] (PHOENIX-5944) Modify the PK of SYSTEM.TASK to
avoid full table scans
[ https://issues.apache.org/jira/browse/PHOENIX-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated PHOENIX-5944:
----------------------------------
Fix Version/s: (was: 4.16.1)
4.16.2
> 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
> Priority: Major
> Fix For: 4.17.0, 4.16.2
>
>
> 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, this change may be to either or both of SYSTEM.TASK_QUEUE and SYSTEM.TASK_HISTORY.
> Note that since this is a PK change, we need to be careful when handling this in the upgrade path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)