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 p
[
https://issues.apache.org/jira/browse/MAPREDUCE-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5788.
Resolution: Not A Problem
Closing as "Not a Problem" given the
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 Mur
I'd like to discuss about some improvements of the sort stage in current
hadoop. There are no formal documents available right now, so I will just
hope someone would be interested in it. If so I can give more detail
information.
To start with, I have conducted a series of experiments on version
