phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-1264) Add StatisticsCollector to existing tables on first connection to cluster
Date Thu, 25 Sep 2014 11:03:33 GMT


ramkrishna.s.vasudevan updated PHOENIX-1264:
    Attachment: Phoenix-1264_2.patch

Patch that solves the test case hanging issue and also found an interesting problem where
because of the new way of issuing <analyze table> using count(*) query the existing
guide posts were being used for the query's execution. Now if there are more than one keyrange
spanning a region the guide post collection for the new rows would happen in batches and this
would mean that the one guideposts updation may delete the other one.  So to fix this if a
query has the new attribute _ANALYZE then do not use the guideposts for it.  
One disadvantage of doing this is that we will end up in doing full region scan as we were
doing with previous endpoints way of analyzing table.

> Add StatisticsCollector to existing tables on first connection to cluster
> -------------------------------------------------------------------------
>                 Key: PHOENIX-1264
>                 URL:
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: Phoenix-1264_1.patch, Phoenix-1264_2.patch
> We'll need to add the StatisticsCollector to existing tables so that stats are kept for
these tables. We typically do that on first connection to the cluster in ensureTableCreated
when our system table is created by walking through the existing Phoenix tables. We only need
to do it if the system table already exists (otherwise, it's a new installation).

This message was sent by Atlassian JIRA

View raw message