phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4007) Surface time at which byte/row estimate information was computed in explain plan output
Date Fri, 15 Sep 2017 17:56:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168264#comment-16168264
] 

Samarth Jain commented on PHOENIX-4007:
---------------------------------------

bq. We no longer report 0 bytes and 0 rows in explain plan when the guidepost width is too
large.
What do we do instead, Samarth Jain?

We don't report 0 bytes and 0 rows. Reporting 0 bytes and 0 rows was a bit misleading in this
case, IMHO.

> Surface time at which byte/row estimate information was computed in explain plan output
> ---------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4007
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4007
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>         Attachments: PHOENIX-4007_v1.patch, PHOENIX-4007_v2.patch, PHOENIX-4007_v3.patch,
PHOENIX-4007_v4.patch, PHOENIX-4007_v6.patch
>
>
> As part of PHOENIX-3822, we surfaced byte and row estimates for queries in explain plan.
Since we collect this information through stats collection, it would also be helpful to surface
when this information was last updated to reflect its freshness. We already store last_stats_update_time
in SYSTEM.STATS. So the task would be essentially surfacing last_stats_update_time as another
column in the explain plan result set.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message