See https://builds.apache.org/job/Hadoop-Common-trunk/1075/changes
Changes:
[wheat9] HDFS-6127. WebHDFS tokens cannot be renewed in HA setup. Contributed
by Haohui Mai.
[vinodkv] MAPREDUCE-2349. Modified FileInputFormat to be able to issue file and
block location calls in parallel.
Joey Echeverria created HADOOP-10414:
Summary: Incorrect property name for RefreshUserMappingProtocol in
hadoop-policy.xml
Key: HADOOP-10414
URL: https://issues.apache.org/jira/browse/HADOOP-10414
I'm clearly supportive of this, though of course the testing costs needed
to back up the assertion make it more expensive than just a statement.
Two issues
-we'd need to make clear that new cluster features that a client can invoke
won't be available. You can't expect snapshot or symlink support
Our use of protobuf helps mitigate a lot of compatibility concerns, but
there still can be situations that require careful coding on our part.
When adding a new field to a protobuf message, the client might need to do
a null check, even if the server-side implementation in the new version
always
+1 for making this guarantee explicit.
It also definitely seems like a good idea to test mixed versions in bigtop.
HDFS is not immune to new client, old server scenarios because the HDFS
client gets bundled into a lot of places.
Colin
On Mar 20, 2014 10:55 AM, Chris Nauroth
Looking forward to the release. What's the state of the application
history server? Do we have security, documentation, and are APIs stable?
If not, do we have a plan for how to make this clear to users?
What about the timeline store?
thanks,
Sandy
On Fri, Mar 14, 2014 at 8:23 PM, Arun C
