Yeah. Would need to define a set of features first. A version would simply 
stand for a distinct set of supported features... I agree that'd be less 
flexible.

      From: Todd Lipcon <t...@cloudera.com>
 To: dev <dev@hbase.apache.org> 
Cc: lars hofhansl <la...@apache.org> 
 Sent: Thursday, March 5, 2015 4:17 PM
 Subject: Re: Client-Server wire compatibility?
   
If you add a negotiation phase, I'd recommend doing it in terms of a
list<SupportedFeature> rather than a version number. That makes it much
easier to backport new features across branches without being forced to
backport all other features that might have been introduced between the two.

-Todd




   

Reply via email to