phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-2706) Implement client-side mechanism to know if stats are enabled
Date Tue, 23 Feb 2016 02:59:18 GMT

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

James Taylor resolved PHOENIX-2706.
-----------------------------------
    Resolution: Fixed

> Implement client-side mechanism to know if stats are enabled
> ------------------------------------------------------------
>
>                 Key: PHOENIX-2706
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2706
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.7.0
>
>         Attachments: PHOENIX-2706.patch, PHOENIX-2706_final.patch
>
>
> Since Phoenix does query planning and explain plan generation on the client-side, we
need a way to distinguish between a table being too small to have stats and stats being disabled.
This new API will provide that on ConnectionQueryServices and be updated in the following
places:
> - during initial cluster connection (ConnectionQueryServices.init()).
> - during UPDATE STATISTICS (based on return value)
> - when guideposts are traversed in BaseResultIterators.getParallelScans(). The value
would only traverse from false to true in this case if we get back guideposts on the PTable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message