[
https://issues.apache.org/jira/browse/HBASE-15016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151411#comment-15151411
]
stack commented on HBASE-15016:
-------------------------------
Ignore the above comment about the SequenceId Interface. It needs flushing out.
It is only used by WALKey yet we have getSequenceId all over the code base.
There is a well-documentted Cell#getSequenceId but I think the doc on it has
gone stale.
Do you need getSequenceId or getNextSequenceId [~eshcar] ? For the latter, we'd
need to block writes and made sure all appended to log (and sync'd to be safe)
before we could let out the 'next' sequenceid.
> StoreServices facility in Region
> --------------------------------
>
> Key: HBASE-15016
> URL: https://issues.apache.org/jira/browse/HBASE-15016
> Project: HBase
> Issue Type: Sub-task
> Reporter: Eshcar Hillel
> Assignee: Eshcar Hillel
> Attachments: HBASE-15016-V01.patch, HBASE-15016-V02.patch,
> HBASE-15016-V03.patch, HBASE-15016-V04.patch, Regioncounters.pdf,
> suggestion.patch
>
>
> The default implementation of a memstore ensures that between two flushes the
> memstore size increases monotonically. Supporting new memstores that store
> data in different formats (specifically, compressed), or that allows to
> eliminate data redundancies in memory (e.g., via compaction), means that the
> size of the data stored in memory can decrease even between two flushes. This
> requires memstores to have access to facilities that manipulate region
> counters and synchronization.
> This subtasks introduces a new region interface -- StoreServices, through
> which store components can access these facilities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
