[
https://issues.apache.org/jira/browse/HBASE-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553040#comment-13553040
]
Enis Soztutar commented on HBASE-7501:
--------------------------------------
Thanks Lars, that was why I wanted clarification. But in the patch, I don't see
the usage of in-region transaction api. The patch just uses batch api.
I am +1 for doing the custom region split policy + use the transaction api. I
guess we've discussed this in some other jira previously. I remember the reason
you did not expose the local trx api, was because we did not want to expose
region boundaries. Maybe it is time to think about how to do it best. Using
prefixes are fine for some use cases, but not all. The problem is that we might
not know the length of the prefixes at all times. One idea is to introduce
something like an entity group to the hbase data model, which is just another
(optional) field, with the semantics of:
- entity groups are exposed and defined by the client. They are optional with
no change in current semantics or performance if not used.
- all records within an entity group are always co-located. Meaning, all
records should be able to fit in a region. Regions are only split at
entity-group boundaries.
- local transactions within an entity group. Local trx api is defined as a
client-api.
- records are sorted with entity-group first, then row key.
- Can be implemented in KV version 2.
> Introduce MetaEditor method that both adds and deletes rows in .META. table
> ---------------------------------------------------------------------------
>
> Key: HBASE-7501
> URL: https://issues.apache.org/jira/browse/HBASE-7501
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Matteo Bertozzi
> Fix For: 0.96.0
>
> Attachments: HBASE-7501-v0.patch, HBASE-7501-v1.patch
>
>
> In review of HBASE-7365, MetaEditor.deleteRegions() and
> MetaEditor.addRegionsToMeta() are used in
> RestoreSnapshotHandler.java.handleTableOperation() to apply changes to .META.
> I made following suggestion:
> Can we introduce new method in MetaEditor which takes List of Mutation's ?
> The Delete and Put would be grouped and then written to .META. table in one
> transaction.
> Jon responded:
> I like that idea -- then the todo/warning or follow on could refer to that
> method. When we fix it, it could get used in other multi row meta
> modifications like splits and table creation/deletion in general.
> See https://reviews.apache.org/r/8674/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
