[
https://issues.apache.org/jira/browse/HBASE-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056201#comment-13056201
]
Mikhail Bautin commented on HBASE-3857:
---------------------------------------
@Stack: no separate migration is needed to go from HFile v1 to HFile v2,
because the new code can read both formats. What we are concerned about is that
if we deploy HFile v2 in production and then get review comments that require a
format change, we might have to migrate from HFile-v2-as-it-currently-is to
HFile-v2-final-with-all-comments-addressed.
> Change the HFile Format
> -----------------------
>
> Key: HBASE-3857
> URL: https://issues.apache.org/jira/browse/HBASE-3857
> Project: HBase
> Issue Type: New Feature
> Reporter: Liyin Tang
> Assignee: Mikhail Bautin
> Attachments: hfile_format_v2_design_draft_0.1.pdf,
> hfile_format_v2_design_draft_0.3.pdf
>
>
> In order to support HBASE-3763 and HBASE-3856, we need to change the format
> of the HFile. The new format proposal is attached here. Thanks for Mikhail
> Bautin for the documentation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
