See https://builds.apache.org/job/Hadoop-Common-trunk/515/
--
[...truncated 26843 lines...]
[DEBUG] (s) debug = false
[DEBUG] (s) effort = Default
[DEBUG] (s) failOnError = true
[DEBUG] (s) findbugsXmlOutput = false
[DEBUG] (s)
[
https://issues.apache.org/jira/browse/HADOOP-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved HADOOP-8060.
Resolution: Fixed
Add a capability to discover and set checksum types per file.
Ivan Mitic created HADOOP-8731:
--
Summary: Public distributed cache support for Windows
Key: HADOOP-8731
URL: https://issues.apache.org/jira/browse/HADOOP-8731
Project: Hadoop Common
Issue Type:
Ivan Mitic created HADOOP-8732:
--
Summary: Address intermittent test failures on Windows
Key: HADOOP-8732
URL: https://issues.apache.org/jira/browse/HADOOP-8732
Project: Hadoop Common
Issue
Ivan Mitic created HADOOP-8733:
--
Summary: TestStreamingTaskLog, TestJvmManager,
TestLinuxTaskControllerLaunchArgs fail on Windows
Key: HADOOP-8733
URL: https://issues.apache.org/jira/browse/HADOOP-8733
(moving to common-dev)
Thanks Harsh,
So what's the final outcome of these changes? Do we get both 32 and 64 bit
libraries in the release tarball? Will they be underneath an arch dir, or
directly under lib/native? I'm just a bit confused because the issue you
reference is:
native libs should
I don't think the latter's been explained or done. Besides, I think
the latter is related more to packaging code (RPMs, etc.) than source
tarballs.
We ship source tarballs in Apache Hadoop releases, and Apache Bigtop
ships/will ship packaged artifacts (going forward). We don't currently
guarantee
Ivan Mitic created HADOOP-8734:
--
Summary: LocalJobRunner does not support private distributed cache
Key: HADOOP-8734
URL: https://issues.apache.org/jira/browse/HADOOP-8734
Project: Hadoop Common
Jason Lowe created HADOOP-8735:
--
Summary: Missing support for dfs.umaskmode
Key: HADOOP-8735
URL: https://issues.apache.org/jira/browse/HADOOP-8735
Project: Hadoop Common
Issue Type: Bug
Brandon Li created HADOOP-8736:
--
Summary: Create a Builder to make an RPC server
Key: HADOOP-8736
URL: https://issues.apache.org/jira/browse/HADOOP-8736
Project: Hadoop Common
Issue Type:
[
https://issues.apache.org/jira/browse/HADOOP-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HADOOP-8735.
Resolution: Duplicate
Missing support for dfs.umaskmode
-
Colin Patrick McCabe created HADOOP-8737:
Summary: cmake: always use JAVA_HOME to find libjvm.so, jni.h,
jni_md.h
Key: HADOOP-8737
URL: https://issues.apache.org/jira/browse/HADOOP-8737
Alejandro Abdelnur created HADOOP-8738:
--
Summary: junit JAR is showing up in the distro
Key: HADOOP-8738
URL: https://issues.apache.org/jira/browse/HADOOP-8738
Project: Hadoop Common
Bikas Saha created HADOOP-8739:
--
Summary: Cmd scripts for Windows have issues in argument parsing
Key: HADOOP-8739
URL: https://issues.apache.org/jira/browse/HADOOP-8739
Project: Hadoop Common
Eli Collins created HADOOP-8740:
---
Summary: Build target to generate findbugs html output
Key: HADOOP-8740
URL: https://issues.apache.org/jira/browse/HADOOP-8740
Project: Hadoop Common
Issue
Hi all,
I just want to know that, based on what factor map reduce framework decides
number of reducers to launch for a job
By default only one reducer will be launched for a given job is this right? If
we explicitly does not mention number to launch via command line or driver
class.
If i
Hi,
On Tue, Aug 28, 2012 at 8:32 AM, Abhishek abhishek.dod...@gmail.com wrote:
Hi all,
I just want to know that, based on what factor map reduce framework decides
number of reducers to launch for a job
The framework does not auto-determine the number of reducers for a
job. That is purely
17 matches
Mail list logo
