hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "Release1.0Requirements" by DougCutting
Date Thu, 02 Oct 2008 20:17:53 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by DougCutting:
http://wiki.apache.org/hadoop/Release1%2e0Requirements

------------------------------------------------------------------------------
  ''Sanjay, How does 'new client application code calling old methods on the !FileSystem'
differ from our current back-compatibility requirements?  --DougCutting''
  
  '' Doug, currently when a new RPC method is added, we declare a change in protocol version
and old and new can no long talk via rpc. There are two issues.  One is the wire compatibility
as you noted (this is new). Second is that when we add new rpc methods, the client side library
can use the new rpc method but it must fall back on old rpc methods when talking to old servers
(this must be explicitly coded in the library -- it won't happen just by introducing wire
compatibility).  You are right in that is nothing new as far as API compatibility.  Maybe
this point is obvious to most, but Owen and I discussed it at some length and thought it was
a subtle twist that our developers will have to be aware of in 1.0.''
+ 
+ ''Sanjay, we should vote on this as a change to our back-compatibility policy, and, if it
passes, start enforcing it.  --DougCutting''
  
  Question: Does the release number really matter?  Should we just keep adding features, improving
back-compatibility, etc?  Our ["Roadmap"] currently defines what a major release means.  Does
this need updating?  -- !DougCutting
  

Mime
View raw message