[
https://issues.apache.org/jira/browse/HBASE-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100513#comment-13100513
]
Lars Hofhansl commented on HBASE-4353:
--------------------------------------
I guess we could have interface with getVersion() and getInstanceVersion(). Or
maybe getClassVersion() and getInstanceVersion().
Then an abstract implementation (getVersion or getClassVersion would be the
abstract method) of that interface pretty close to what VersionedWritable does.
That class would also implement Writable.
In the HLogKey case, it would not subclass the abstract class, but just
implement the interface.
If that's the route we want to take... Need to come up with good names for the
interface and the abstract class.
And should existing versioned things (HRegion, WALEdit, etc, etc) be refactored
into this?
(Just brainstorming here :) )
> 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
