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] [Updated] (PHOENIX-4007) Surface time at which byte/row estimate information was computed in explain plan output
Date Tue, 26 Sep 2017 07:34:00 GMT

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

Samarth Jain updated PHOENIX-4007:
----------------------------------
    Attachment: PHOENIX-4007_v10.patch

Thanks for the feedback, James. Hopefully this should do it. I had to resort to adding some
extra state in DefaultStatisticsCollector just so that we can initialize statsWriter later.
Not the biggest fan of this approach, but I am not sure what else can be done.

> 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_v10.patch, PHOENIX-4007_v1.patch, PHOENIX-4007_v2.patch,
PHOENIX-4007_v3.patch, PHOENIX-4007_v4.patch, PHOENIX-4007_v6.patch, PHOENIX-4007_v7.patch,
PHOENIX-4007_v8.patch, PHOENIX-4007_v9.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