Re: Release numbering for branch-2 releases

On Tue, Jan 29, 2013 at 12:56 PM, Arun C Murthy wrote: > Folks, > > There has been some discussions about incompatible changes in the > hadoop-2.x.x-alpha releases on HADOOP-9070, HADOOP-9151, HADOOP-9192 and > few other jiras. Frankly, I'm surprised about some of them since the > 'alpha' monike

Re: Release numbering for branch-2 releases

Hi Arun, et. al., I hope you don't mind a non-contributor butting in here. I'm currently a Hadoop administrator and former application developer (non-hadoop). regarding GA release changes, I think Arun has got a lot of good ideas here. I think it's better to add new features via new flags, para

Re: Release numbering for branch-2 releases

The discussions in HADOOP-9151 were related to wire-compatibility. I think we all agree that breaking API compatibility is not allowed without deprecating them first in a prior major release - this is something we have followed since hadoop-0.1. I agree we need to spell out what changes we can

Re: Release numbering for branch-2 releases

Thanks for bringing this up Arun. One of the issues is that we haven't been clear about what type of compatibility breakages are allowed, and which are not. For example, renaming FileSystem#open is incompatible, and not OK, regardless of the alpha/beta tag. Breaking a server/server APIs is OK pr

[jira] [Created] (HDFS-4457) WebHDFS obtains/sets delegation token service hostname using wrong config leading to issues when NN is configured with 0.0.0.0 RPC IP

Alejandro Abdelnur created HDFS-4457: Summary: WebHDFS obtains/sets delegation token service hostname using wrong config leading to issues when NN is configured with 0.0.0.0 RPC IP Key: HDFS-4457 URL: https://

[jira] [Resolved] (HDFS-4212) NameNode can't differentiate between a never-created block and a block which is really missing

[ https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li resolved HDFS-4212. -- Resolution: Duplicate > NameNode can't differentiate between a never-created block and a block which

Re: Release numbering for branch-2 releases

I still have a list of pending API/protocol cleanup in YARN that need to be in before we even attempt supporting compatibility further down the road. There's no way we can support wire compatibility with the APIs in the state that they are in now. So, +1 for a beta sometime in March. There are som

[jira] [Resolved] (HDFS-3598) WebHDFS: support file concat

[ https://issues.apache.org/jira/browse/HDFS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-3598. -- Resolution: Fixed > WebHDFS: support file concat > -

[jira] [Created] (HDFS-4456) Update WebHDFS REST API for concat

Tsz Wo (Nicholas), SZE created HDFS-4456: Summary: Update WebHDFS REST API for concat Key: HDFS-4456 URL: https://issues.apache.org/jira/browse/HDFS-4456 Project: Hadoop HDFS Issue Ty

[jira] [Reopened] (HDFS-3598) WebHDFS: support file concat

[ https://issues.apache.org/jira/browse/HDFS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur reopened HDFS-3598: -- This patch is incomplete, 2 issues: * It is not updating the WebHDFS spec/doc. * It is not

Jenkins build is back to normal : Hadoop-Hdfs-0.23-Build #510

See