[jira] [Resolved] (HADOOP-7798) Release artifacts need to be signed for Nexus

[ https://issues.apache.org/jira/browse/HADOOP-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved HADOOP-7798. --- Resolution: Fixed I just committed this. Thanks Doug! Also thanks to Giri and Bruno.

[jira] [Created] (HADOOP-7800) Could not find source jars in dist tarball

Could not find source jars in dist tarball -- Key: HADOOP-7800 URL: https://issues.apache.org/jira/browse/HADOOP-7800 Project: Hadoop Common Issue Type: Bug Components: build Affects Vers

Re: FileSystem contract of listStatus

Perhaps fixes against this can be covered as part of https://issues.apache.org/jira/browse/HADOOP-7659 On 03-Nov-2011, at 5:44 AM, Ted Dunning wrote: > I think that the API docs actually say globStatus is ordered and leave the > ordering semantics for listStatus undefined. > > http://hadoop.apa

Re: FileSystem contract of listStatus

I think that the API docs actually say globStatus is ordered and leave the ordering semantics for listStatus undefined. http://hadoop.apache.org/common/docs/r0.20.2/api/org/apache/hadoop/fs/FileSystem.html#globStatus(org.apache.hadoop.fs.Path) http://hadoop.apache.org/common/docs/r0.20.2/api/org/

Re: FileSystem contract of listStatus

- Original Message - > From: "Eli Collins" > > RawLocalFileSystem uses Java's File#list which has "no guarantee that > the name strings in the resulting array will appear in any specific > order; they are not, in particular, guaranteed to appear in > alphabetical order.", however the FSCon

Re: FileSystem contract of listStatus

Hey Noah, HDFS returns items in lexographic order by byte (see INode#compareBytes) but I don't think ordering was intended to be an explicit part of the contract. Ie the test probably just needs to be modified to ignore the order. RawLocalFileSystem uses Java's File#list which has "no guarantee t

FileSystem contract of listStatus

I have a question about the FileSystem contract in 0.20. In FileSystemContractBaseBaseTest:testFileStatus() there are several files created, and afterwards the test confirms that they are present. Here is the relevant code: FileStatus[] paths = fs.listStatus(path("/test")); paths = fs.li

[jira] [Created] (HADOOP-7799) Improvements to Doc: Hadoop MapReduce Next Generation - Cluster Setup

Improvements to Doc: Hadoop MapReduce Next Generation - Cluster Setup - Key: HADOOP-7799 URL: https://issues.apache.org/jira/browse/HADOOP-7799 Project: Hadoop Common Issue

[jira] [Resolved] (HADOOP-4177) Range of ports instead of all over the map

[ https://issues.apache.org/jira/browse/HADOOP-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-4177. -- Resolution: Won't Fix Ops teams are expected to reconfigure the ports via the configur

[jira] [Resolved] (HADOOP-5670) Hadoop configurations should be read from a distributed system

[ https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-5670. -- Resolution: Won't Fix > Hadoop configurations should be read from a distributed sy

[jira] [Resolved] (HADOOP-6258) Native compilation assumes gcc

[ https://issues.apache.org/jira/browse/HADOOP-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6258. -- Resolution: Won't Fix Hadoop is not focused on portability. Closing as won't fix.

[jira] [Resolved] (HADOOP-6210) Bind Hadoop RPC outgoing to a specific nic

[ https://issues.apache.org/jira/browse/HADOOP-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6210. -- Resolution: Won't Fix > Bind Hadoop RPC outgoing to a specific nic > -

[jira] [Resolved] (HADOOP-6264) list of variables usable in configuration files is undocumented outside the source code

[ https://issues.apache.org/jira/browse/HADOOP-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6264. -- Resolution: Won't Fix > list of variables usable in configuration files is undocum

[jira] [Resolved] (HADOOP-6294) log4j settings are service/node specific

[ https://issues.apache.org/jira/browse/HADOOP-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6294. -- Resolution: Won't Fix Ops teams are expected to have multiple, different configuration

[jira] [Resolved] (HADOOP-6295) Build process from tarball is flawed

[ https://issues.apache.org/jira/browse/HADOOP-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6295. -- Resolution: Won't Fix > Build process from tarball is flawed > ---

[jira] [Resolved] (HADOOP-6445) distcp -p doesn't work when run on destination

[ https://issues.apache.org/jira/browse/HADOOP-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6445. -- Resolution: Won't Fix > distcp -p doesn't work when run on destination > -

[jira] [Resolved] (HADOOP-6364) add a 'hostname' or 'identity' parameter

[ https://issues.apache.org/jira/browse/HADOOP-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6364. -- Resolution: Won't Fix Hadoop isn't focused on servers with multiple interfaces. Closin

[jira] [Resolved] (HADOOP-6491) JAVA_PLATFORM in hadoop shell script lacks HADOOP_OPTS

[ https://issues.apache.org/jira/browse/HADOOP-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6491. -- Resolution: Won't Fix Building our own hadoop shell scripts. Closing as won't fix.

[jira] [Resolved] (HADOOP-6516) Distch is not documented?

[ https://issues.apache.org/jira/browse/HADOOP-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-6516. -- Resolution: Won't Fix > Distch is not documented? > - > >

[jira] [Created] (HADOOP-7798) Release artifacts need to be signed for Nexus

Release artifacts need to be signed for Nexus - Key: HADOOP-7798 URL: https://issues.apache.org/jira/browse/HADOOP-7798 Project: Hadoop Common Issue Type: Bug Components: build Affect

[jira] [Resolved] (HADOOP-7386) Support concatenated bzip2 files

[ https://issues.apache.org/jira/browse/HADOOP-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7386. -- Resolution: Won't Fix > Support concatenated bzip2 files > ---

[jira] [Resolved] (HADOOP-7405) libhadoop is all or nothing

[ https://issues.apache.org/jira/browse/HADOOP-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-7405. -- Resolution: Won't Fix Hadoop is not focused on portability. > libhado

Build failed in Jenkins: Hadoop-Common-0.23-Build #54

See Changes: [szetszwo] Revert the previous commit 1196436 for HDFS-2416. [szetszwo] svn merge -c 1196434 from trunk for HDFS-2416. [acmurthy] Merge -r 1196410:1196412 from trunk to branch-0.23 to fix HADOOP-7789. [mahadev] M

[jira] [Created] (HADOOP-7797) Fix the repository name to support pushing to the staging area of Nexus

Fix the repository name to support pushing to the staging area of Nexus --- Key: HADOOP-7797 URL: https://issues.apache.org/jira/browse/HADOOP-7797 Project: Hadoop Common Is