[
https://issues.apache.org/jira/browse/HBASE-11762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099824#comment-14099824
]
Andrew Purtell edited comment on HBASE-11762 at 8/16/14 11:23 PM:
------------------------------------------------------------------
Instead of returning a String or Pair containing the new configuration
information you'd like to pass around, how about creating a WALContext (or
similarly named) object that we can further extend if there are more variations
we have to deal with in the future viz reader/writer classes, codec classes,
etc. ?
was (Author: apurtell):
Instead of returning a String or Pair containing the new configuration
information you'd like to pass around, how about creating a WALConfig (or
similarly named) object that we can further extend if there are more variations
we have to deal with in the future viz reader/writer classes, codec classes,
etc. ?
> Record the class name of Codec in WAL header
> --------------------------------------------
>
> Key: HBASE-11762
> URL: https://issues.apache.org/jira/browse/HBASE-11762
> Project: HBase
> Issue Type: Task
> Components: wal
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Attachments: 11762-v1.txt, 11762-v2.txt
>
>
> In follow-up discussion to HBASE-11620, Enis brought up this point:
> Related to this, should not we also write the CellCodec that we use in the
> WAL header. Right now, the codec comes from the configuration which means
> that you cannot read back the WAL files if you change the codec.
> This JIRA is to implement the above suggestion.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
