[
https://issues.apache.org/jira/browse/HBASE-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102392#comment-13102392
]
Lars Hofhansl commented on HBASE-4353:
--------------------------------------
Now that I think about it. The static class version should not need to visible
outside of the versioned object. I.e. the class should know internally what
version is supports, but outside code only needs to know about the instance
version (if at all), unless we deal with loadable jars, where the surrounding
code may need to determine the static version the class is at.
That is actually what bothers me about VersionedWritable, that getVersion()
needs to be return the class version of it to work correctly.
> 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
