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-1453) Collect row counts per region in stats table
Date Wed, 26 Nov 2014 06:11:13 GMT

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

James Taylor commented on PHOENIX-1453:
---------------------------------------

It's fine if you update the SYSTEM.STATS table with the ROW_COUNT information. That won't
have an impact on backward compat. Just make sure that an pre 4.3 client can still read the
protobuf for a PTable with or with/out the new row count information. I don't think there's
really any b/w compat issue you need to worry about.

> Collect row counts per region in stats table
> --------------------------------------------
>
>                 Key: PHOENIX-1453
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1453
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: Phoenix-1453.patch, Phoenix-1453_1.patch, Phoenix-1453_2.patch
>
>
> We currently collect guideposts per equal chunk, but we should also capture row counts.
Should we have a parallel array with the guideposts that count rows per guidepost, or is it
enough to have a per region count?



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

Mime
View raw message