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-4700) Fix split policy on system tables other than SYSTEM.CATALOG
Date Wed, 25 Apr 2018 15:02:00 GMT

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

James Taylor commented on PHOENIX-4700:
---------------------------------------

bq. why do we need a split policy for SYSTEM.STATS?
When we write stats, we use the multi-row HBase coprocessor API to make the write atomic (both
delete of old stats and add of new stats is done in one call). If these rows spanned across
a region, the call would fail. We could change is to either make one call per cf still using
same technique (and allow split per table+cf) or to just use regular batch API at the expense
of potential inconsistencies on a write failure.

> Fix split policy on system tables other than SYSTEM.CATALOG
> -----------------------------------------------------------
>
>                 Key: PHOENIX-4700
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4700
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4700.patch, PHOENIX-4700_wip1.patch
>
>
> The MetaDataSplitPolicy was changed to cause a table to never split. This is the right
thing to do for SYSTEM.CATALOG, but not for the other system tables that use it. We need to
create a new split policy as it was before for these other system tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message