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, 31 Dec 2014 05:50:15 GMT

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

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

Let's just keep it simple for now: leave the byte count as is (it's the
total byte count across all regions), and keep only a single row count on
the GuidePostInfo as the total row count across all regions. The
addColumnsIfNotExists
takes a String arg that's the column and type name separated be a space -
just look at examples of other usages (and please test manually).


> 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_10.patch,
Phoenix-1453_2.patch, Phoenix-1453_3.patch, Phoenix-1453_7.patch, Phoenix-1453_8.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