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] [Commented] (PHOENIX-3361) Collect stats correctly for local indexes
Date Mon, 10 Oct 2016 19:48:20 GMT

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

James Taylor commented on PHOENIX-3361:
---------------------------------------

That's true about TestUtil#dumpTable, but I keep having to write that again when I need it,
so I thought I'd just leave it in TestUtil instead.

> Collect stats correctly for local indexes
> -----------------------------------------
>
>                 Key: PHOENIX-3361
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3361
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.9.0
>
>         Attachments: PHOENIX-3361.patch, PHOENIX-3361_wip.patch, PHOENIX-3361_wip2.patch
>
>
> Stats are not being correctly collected for local indexes and tables with local indexes,
because the logic that deletes the old stats is based on all store families of a table. Thus,
when stats are collected for a table with local indexes, the local index stats would be deleted
and when the stats for a local index are collected, the stats for the table will be deleted.
> Instead, if we cache stats per column family instead of across entire table, plus detect
if we're collecting stats for a local index versus the data table, we can fix this issue.
Caching stats per column family makes more sense anyway, because depending on the query, we
may only use the stats associated with the default column family. Also, we wouldn't want to
have to pull over stats for local index with the data table stats.



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

Mime
View raw message