[
https://issues.apache.org/jira/browse/HBASE-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702956#comment-13702956
]
ramkrishna.s.vasudevan commented on HBASE-8849:
-----------------------------------------------
bq.The codec used writing would be metadata on the hfile. You'd read what codec
to use before you started pulling in blocks
Yes true. We will be able to do this, should not be a problem.
bq.The file would be wrriten w/ a codec that included mvcc or it could be
written with a codec that did not include mvcc?
Hmmm.. Yes.. We can have this. But the read and write flow should be able to
know about this and the framework that will be using the codec should take the
decision of how to handle the mvcc. Am i making it clear?
So the framework should be intelligent enough to know this and work based on
that. Which i thought would make the read/write path to have additional code
incase mvcc is not handled inside the codec.
> CellCodec should write and read the memstoreTS/mvccVersion
> ----------------------------------------------------------
>
> Key: HBASE-8849
> URL: https://issues.apache.org/jira/browse/HBASE-8849
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Labels: keyvalue
> Fix For: 0.98.0
>
> Attachments: HBASE-8849_1.patch, HBASE-8849_2.patch
>
>
> This JIRA is wrt discussion over in HBASE-8496.
> Cell interface and the corresponding CellCodec provides a new way of
> serializing the Keyvalues.
> Cell interface supports getMvccVersion() and the javadoc says it could be > 0
> if it exists or 0 otherwise.
> But we don't tend to write/read the memstoreTS/mvccVersion in the Cell codec.
--
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
