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 2024/07/19 20:45:00 UTC

[jira] [Updated] (PHOENIX-7365) ExplainPlanV2 should get trimmed list for regionserver location

     [ https://issues.apache.org/jira/browse/PHOENIX-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viraj Jasani updated PHOENIX-7365:
----------------------------------
    Fix Version/s: 5.1.4

> ExplainPlanV2 should get trimmed list for regionserver location
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-7365
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7365
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 5.2.0
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 5.2.1, 5.3.0, 5.1.4
>
>
> PHOENIX-6907 introduces way for ExplainPlan to provide list of regionserver locations that are accessed by the query during execution. It also introduces config "phoenix.max.region.locations.size.explain.plan" to restrict max region locations to be displayed as part of the Explain plan output. However, the trimmed list was intentionally meant for query output version of ExplainPlan only, not for ExplainPlanV2 based explain plan output.
> However, given the convenience provided by ExplainPlanV2 objects, it is far easier to use it by client applications rather than breaking down the String based old explain plan. It would be better to keep trimmed list of regionserver for ExplainPlanV2 as well, rather than keeping full list around in the objects.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)