[jira] [Resolved] (HADOOP-8126) [Coprocessors] Add hooks for bulk loading actions

[ https://issues.apache.org/jira/browse/HADOOP-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HADOOP-8126. Resolution: Invalid Note to self: Don't try to open jiras on the iPhone.

[jira] [Created] (HADOOP-8126) [Coprocessors] Add hooks for bulk loading actions

[Coprocessors] Add hooks for bulk loading actions - Key: HADOOP-8126 URL: https://issues.apache.org/jira/browse/HADOOP-8126 Project: Hadoop Common Issue Type: Improvement Reporter:

Re: Developing and deploying hadoop

a) Standard practice is to keep data directory independent of program directory. For example, if the software is installed in /opt/hadoop/hadoop-1.0. Data may be located in /var/hadoop. When new version is available for deployment, it can be deployed to /opt/hadoop/hadoop-2.0 and use the same /v

Re: Developing and deploying hadoop

Hi! One way to deploy Hadoop in a more formal environment is to do it via the Bigtop distribution. Bigtop provides packages and puppet deployment code for most Linux distributions. We try to make the experience of deploying Hadoop as seamless as possible, since our goal can be summarized as "tryin

Re: Developing and deploying hadoop

I would be glad to hear what is your development cycle and how you deploy new features to production cluster... How do you deploy them to the production cluster? With bash scripts and rsync, ant, maven or any other automation tool? I would be thankfull if you could point me to any resource describ

[jira] [Created] (HADOOP-8125) make hadoop-client set of curated jars available in a distribution tarball

make hadoop-client set of curated jars available in a distribution tarball -- Key: HADOOP-8125 URL: https://issues.apache.org/jira/browse/HADOOP-8125 Project: Hadoop Common

[jira] [Created] (HADOOP-8124) Remove the deprecated Syncable.sync() method

Remove the deprecated Syncable.sync() method Key: HADOOP-8124 URL: https://issues.apache.org/jira/browse/HADOOP-8124 Project: Hadoop Common Issue Type: Improvement Components: fs

[jira] [Created] (HADOOP-8123) hadoop-project invalid pom warnings prevent transitive dependency resolution

hadoop-project invalid pom warnings prevent transitive dependency resolution Key: HADOOP-8123 URL: https://issues.apache.org/jira/browse/HADOOP-8123 Project: Hadoop Common

[jira] [Created] (HADOOP-8122) Build should fail when compilation .proto files fail

Build should fail when compilation .proto files fail Key: HADOOP-8122 URL: https://issues.apache.org/jira/browse/HADOOP-8122 Project: Hadoop Common Issue Type: Bug Components: bu

[jira] [Created] (HADOOP-8121) Active Directory Group Mapping Service

Active Directory Group Mapping Service -- Key: HADOOP-8121 URL: https://issues.apache.org/jira/browse/HADOOP-8121 Project: Hadoop Common Issue Type: New Feature Components: security R

[Important] Checksum Error while appending to the file.

Hi All, In one of our hadoop cluster we faced CheckSum file Corruption, due to which appending to the file failed. If any one of you faced this problem earlier, please share your experiences. We are using hadoop 0.20.1 with append feature. Scenario: === 1. Created the file, wri

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

See Changes: [vinodkv] MAPREDUCE-3931. Changed PB implementation of LocalResource to take locks so that race conditions don't fail tasks by inadvertantly changing the timestamps. Contributed by Siddarth Seth. svn merge --ignor

Jenkins build is back to normal : Hadoop-Common-0.23-PB-Build #7

See