[
https://issues.apache.org/jira/browse/HBASE-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100532#comment-13100532
]
Ted Yu commented on HBASE-4353:
-------------------------------
I think DoubleVersionedWritable may not be a good name.
We can name the interface WritableWithVersions. Since it lives inside
org.apache.hadoop.hbase namespace, it is easy to distinguish with
VersionedWritable.
If HLogKey only implements this interface, there is no hurry in creating the
abstract class.
In fact, I am not sure the abstract class should assume version being a byte.
> Create VersionedWritable interface that allows a class version and an
> instance version
> --------------------------------------------------------------------------------------
>
> Key: HBASE-4353
> URL: https://issues.apache.org/jira/browse/HBASE-4353
> Project: HBase
> Issue Type: New Feature
> Reporter: Ted Yu
>
> Here is comment from Lars (HBASE-2195):
> When we did versioning for a project I used to work on a long time ago, we
> had maintained a class version *and* an instance version. We might need both.
> The class should know which version it is, but also it is useful in many
> scenarios to ask the instance what specific version it is on.
> I.e. we need an interface with two methods: One to get the class version, one
> to get the instance version.
> This would apply to HLogKey which is able to read entries without explicit
> version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
