[
https://issues.apache.org/jira/browse/HBASE-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349519#comment-14349519
]
Lars Hofhansl commented on HBASE-13159:
---------------------------------------
In our case we'd want to share *initial* data between tenants. The next
compaction (if the other tenant changes data) would cause the data to be
rewritten, that's how we'd want it. (or maybe we'd want to optionally block
these reference files from being compacted).
Might be very specific to our use case.
Bulk delete and update by declaring a transformation is also very interesting.
> Consider RangeReferenceFiles with transformations
> -------------------------------------------------
>
> Key: HBASE-13159
> URL: https://issues.apache.org/jira/browse/HBASE-13159
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Lars Hofhansl
>
> Currently we have References used by HalfStoreReaders and HFileLinks.
> For various use cases we have here we have need for a RangeReferences with
> simple transformation of the keys.
> That would allow us to map HFiles between regions or even tables without
> copying any data.
> We can probably combine HalfStores, HFileLinks, and RangeReferences into a
> single concept:
> * RangeReference = arbitrary start and stop row, arbitrary key transformation
> * HFileLink = start and stop keys set to the linked file's start/stop key,
> transformation = identity
> * (HalfStore) References = start/stop key set according to top or bottom
> reference, transformation = identity
> Note this is a *brainstorming* issue. :)
> (Could start with just references with arbitrary start/stop keys, and do
> transformations later)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
