tion of configs - potentially separating client side
> configs
> >> and those used by daemons. This is another source of perpetual confusion
> >> for users.
> >>
> >> Thanks
> >> - Sid
> >>
> >>
> >> On Thu, Mar 5, 2015 at 2:46 PM, S
IMO, if part of the community wants to take on the responsibility and work
that takes to do a new major release, we should not discourage them from
doing that.
Having multiple major branches active is a standard practice.
This time around we are not replacing the guts as we did from Hadoop 1 to
H
IMO we should:
1* have a clean and thin client API JAR (which does not drag any 3rd party
dependencies, or a well defined small set -i.e. slf4j & log4j-)
2* have a client implementation that uses a classloader to isolate client
impl 3rd party deps from app dependencies.
#2 can be done using a sto
--
Alejandro
Alejandro Abdelnur created HDFS-7074:
Summary: KMS: KeyAuthorizationKeyProvider should verify the
keyversion belongs to the keyname on decrypt
Key: HDFS-7074
URL: https://issues.apache.org/jira/browse/HDFS
Thanks Karthik.
+1.
+ verified MD5 for source tarball
+ verified signature for source tarball
+ successfully run apache-rat:check
+ checked CHANGES, LICENSE, README, NOTICE files.
+ built from source tarball
+ started pseudo cluster
+ run a couple of MR example jobs
+ basic test on HttpFS
On Wed
Alejandro Abdelnur created HDFS-7006:
Summary: Test encryption zones with MKS
Key: HDFS-7006
URL: https://issues.apache.org/jira/browse/HDFS-7006
Project: Hadoop HDFS
Issue Type: Test
Alejandro Abdelnur created HDFS-6986:
Summary: DistributedFileSystem must get deletagiontokens from
configured KeyProvider
Key: HDFS-6986
URL: https://issues.apache.org/jira/browse/HDFS-6986
I've just did some work on top of trunk and branch-2, all good.
Thanks Karthik.
On Tue, Aug 26, 2014 at 2:26 PM, Karthik Kambatla
wrote:
> I compared the new asf git repo against the svn and github repos (mirrored
> from svn). Here is what I see:
> - for i in *; do git diff $i ../hadoop-githu
Alejandro Abdelnur created HDFS-6909:
Summary: KeyProviderCryptoExtension should use CryptoCodec for
generation/decryption of keys
Key: HDFS-6909
URL: https://issues.apache.org/jira/browse/HDFS-6909
[
https://issues.apache.org/jira/browse/HDFS-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HDFS-3988.
--
Resolution: Done
HADOOP-10771 took care of this.
> HttpFS can't do GETDELEGAT
Verified MD5s and signatures of both SRC & BIN tarballs.
Thanks Karthik.
On Mon, Aug 18, 2014 at 12:42 PM, Karthik Kambatla
wrote:
> Hi devs
>
> Tsuyoshi just brought it to my notice that the published tarballs don't
> have LICENSE, NOTICE and README at the top-level. Instead, they are only
>
+1
Alejandro
(phone typing)
> On Aug 8, 2014, at 19:57, Karthik Kambatla wrote:
>
> I have put together this proposal based on recent discussion on this topic.
>
> Please vote on the proposal. The vote runs for 7 days.
>
> 1. Migrate from subversion to git for version control.
> 2. Force-
lan, and has already identified a few issues that have
> been
> > fixed.
> >
> > Design and development of this feature was also a cross-company effort
> > with many different contributors.
> >
> > I'd like to thank Charles Lamb, Yi Liu, Uma Maheswar
funny, i'd treat it as a merge vote.
On Fri, Aug 8, 2014 at 11:44 AM, Karthik Kambatla
wrote:
> Thanks Steve. Including that in the proposal.
>
> By the way, from our project bylaws (http://hadoop.apache.org/bylaws.html
> ),
> I can't tell what kind of a vote this would be.
>
>
> On Thu, Aug 7,
+0, (see 2 '-' below). I think we should address those and cut a new RC.
+ verified MD5 for source tarball
+ verified signature for source tarball
+ successfully run apache-rat:check
- CHANGES.txt have 'Release 2.5.0 - UNRELEASED' they should have 'Release
2.5.0 - '
- HDFS CHANGES.txt has HDFS-675
I would say we can first move to git and keep the very same workflow we
have today, then we can evolve it.
On Tue, Aug 5, 2014 at 6:46 PM, Arpit Agarwal
wrote:
> +1 to voting on specific workflow(s).
>
>
> On Tue, Aug 5, 2014 at 5:49 PM, Karthik Kambatla
> wrote:
>
> > If we are to start a vot
Alejandro Abdelnur created HDFS-6826:
Summary: Plugin interface to enable delegation of HDFS
authorization assertions
Key: HDFS-6826
URL: https://issues.apache.org/jira/browse/HDFS-6826
Project
+1, we did it for Oozie a while back and was painless with minor issues in
Jenkins jobs
Rebasing feature branches on latest trunk may be tricky as that may require
a force push and if I'm not mistaken force pushes are disabled in Apache
GIT.
thx
On Fri, Aug 1, 2014 at 4:43 PM, Karthik Kambatla
> What's in branch-2.4.1 doesn't currently match what's in this RC,
but there is a tag that matches, right? Else we need to fix that.
On Fri, Jun 27, 2014 at 3:26 PM, Aaron T. Myers wrote:
> That's fine by me. Like I said, assuming that rc1 does indeed include the
> fix in HDFS-6527, and not t
; Hortonworks
> http://hortonworks.com/
>
>
>
> On Wed, Jun 25, 2014 at 9:48 AM, Owen O'Malley wrote:
>
> > On Tue, Jun 24, 2014 at 4:44 PM, Alejandro Abdelnur
> > wrote:
> >
> > > After reading this thread and thinking a bit about it, I t
After reading this thread and thinking a bit about it, I think it should be
OK such move up to JDK7 in Hadoop 2 for the following reasons:
* Existing Hadoop 2 releases and related projects are running
on JDK7 in production.
* Commercial vendors of Hadoop have already done lot of
work to ensure
On Fri, Jun 20, 2014 at 10:02 PM, Arun C Murthy wrote:
> > Hadoop 3.x out the door later this year
>
> +1 that makes sense to me. Thanks for volunteering Steve - I'm glad to
> share the pain… ;-)
Hey Arun, you may have missed that Andrew volunteered for doing this as
well (the thread is long,
+1
verified checksum & signature on SRC TARBALL
verified CHANGES.txt files
run apache-rat:check on SRC
build SRC
installed pseudo cluster
run successfully a few MR sample jobs
verified HttpFS
Thanks Arun
On Mon, Jun 16, 2014 at 9:27 AM, Arun C Murthy wrote:
> Folks,
>
> I've created a releas
Alejandro Abdelnur created HDFS-6391:
Summary: Get the Key/IV from the NameNode for encrypted files in
DFSClient
Key: HDFS-6391
URL: https://issues.apache.org/jira/browse/HDFS-6391
Project
Alejandro Abdelnur created HDFS-6390:
Summary: chown/chgrp users/groups blacklist for encrypted files
Key: HDFS-6390
URL: https://issues.apache.org/jira/browse/HDFS-6390
Project: Hadoop HDFS
Alejandro Abdelnur created HDFS-6387:
Summary: HDFS CLI admin tool for creating & deleting an encryption
zone
Key: HDFS-6387
URL: https://issues.apache.org/jira/browse/HDFS-6387
Project: Ha
[
https://issues.apache.org/jira/browse/HDFS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HDFS-3011.
--
Resolution: Won't Fix
[doing self-clean up of JIRAs], with new hdfs ui i don&#x
Alejandro Abdelnur created HDFS-6394:
Summary: HDFS encryption documentation
Key: HDFS-6394
URL: https://issues.apache.org/jira/browse/HDFS-6394
Project: Hadoop HDFS
Issue Type: Sub-task
Alejandro Abdelnur created HDFS-6392:
Summary: Wire crypto streams for encrypted files in DFSClient
Key: HDFS-6392
URL: https://issues.apache.org/jira/browse/HDFS-6392
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HDFS-2097.
--
Resolution: Invalid
[doing self-clean up of JIRAs] closing as invalid as this has been
Alejandro Abdelnur created HDFS-6386:
Summary: HDFS Encryption Zones
Key: HDFS-6386
URL: https://issues.apache.org/jira/browse/HDFS-6386
Project: Hadoop HDFS
Issue Type: Sub-task
Alejandro Abdelnur created HDFS-6388:
Summary: HDFS integration with KeyProvider
Key: HDFS-6388
URL: https://issues.apache.org/jira/browse/HDFS-6388
Project: Hadoop HDFS
Issue Type: Sub
Alejandro Abdelnur created HDFS-6404:
Summary: HttpFS should use a 000 umask for mkdir and create
operations
Key: HDFS-6404
URL: https://issues.apache.org/jira/browse/HDFS-6404
Project: Hadoop
Alejandro Abdelnur created HDFS-6389:
Summary: Rename restrictions for encryption zones
Key: HDFS-6389
URL: https://issues.apache.org/jira/browse/HDFS-6389
Project: Hadoop HDFS
Issue
HDFS devs,
I've just created the branch fs-encryption for HADOOP-10150 and HDFS-6134
work.
Thanks.
--
Alejandro
Alejandro Abdelnur created HDFS-6393:
Summary: User settable xAttr to stop HDFS admins from
reading/chowning a file
Key: HDFS-6393
URL: https://issues.apache.org/jira/browse/HDFS-6393
Project
[
https://issues.apache.org/jira/browse/HDFS-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur reopened HDFS-6134:
--
[cross-posting with HADOOP-10150]
Reopening HDFS-6134
After some offline discussions with
Alejandro Abdelnur created HDFS-6379:
Summary: HTTPFS - Implement ACLs support
Key: HDFS-6379
URL: https://issues.apache.org/jira/browse/HDFS-6379
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HDFS-6134.
--
Resolution: Duplicate
[Cross-posting with HADOOP-10150, closing this JIRA as duplicate
Haouhi's suggestion of a hdfs-client JAR with client dependencies only,
would be IMO the 'correct' way of doing things, we should have a
hdfs-server and hdfs-client JARs.
Doing this is practice is not trivial as classes are not properly
segregated. So, Steven's suggestion of an hdfs-client seems
Alejandro Abdelnur created HDFS-6134:
Summary: Transparent data at rest encryption
Key: HDFS-6134
URL: https://issues.apache.org/jira/browse/HDFS-6134
Project: Hadoop HDFS
Issue Type
Trying to run the PI MapReduce example using RC0 the job is failing,
looking at the NM logs I'm getting the following.
I believe it may be something in my setup as many already test MR jobs with
this RC successfully, but couldn't figure out yet. Running on OSX 10.9.1
using JDK7.
Thanks.
--
Running pseudo cluster out of the box (expanding the binary tar, or
building from source) does not work, you have to go an set the MR framework
to yarn, the default FS URI to hdfs://localhost:8020, and so on.
While I don't see this as showstopper (for the knowledgeable user), it will
make may user
sire, as sandy said, lets keep it in branch 2 for now and if not resolved by
2.4 timeframe we'll revert them there.
thx
Alejandro
(phone typing)
> On Feb 7, 2014, at 10:14, Steve Loughran wrote:
>
>> On 6 February 2014 17:07, Alejandro Abdelnur wrote:
>>
>&
care of those issues.
>
> +1 for going ahead with the revert on branch-2.3. I'll go do that tomorrow
> morning unless I hear otherwise from Jian.
>
> Thanks,
> +Vinod
>
>
> On Feb 6, 2014, at 8:28 PM, Alejandro Abdelnur wrote:
>
> > Hi Vinod,
> >
>
t decision.
>
> There is the issue with unmanaged AM that is clearly known and I was
> thinking of coming to the past two days, but couldn't. What is this new
> issue that we (confidently?) pinned down to YARN-1490?
>
> Thanks
> +Vinod
>
> On Feb 6, 2014, at 5:07 PM, Ale
roblem caused by YARN-1493 I think we can revert it in branch-2.3 as well.
>>
>> I think we should leave them in branch-2 for now. We can revert if 2.4 is
>> imminent and they're holding it up, but hopefully the issues they caused
>> will be fixed by then.
> >
> > >
> > > On Wed, Feb 5, 2014 at 4:49 PM, Arpit Agarwal <
> aagar...@hortonworks.com
> > > >wrote:
> > >
> > > > IMO HADOOP-10273 (Fix 'mvn site') should be included in 2.3.
> > > >
> > > > I will merge it to
IMO YARN-1577 is a blocker, it is breaking unmanaged AMs in a very odd ways
(to the point it seems un-deterministic).
I'd say eiher YARN-1577 is fixed or we revert
YARN-1493/YARN-1490/YARN-1166/YARN-1041/YARN-1566 (almost clean reverts)
from Hadoop 2.3 branch before doing the release.
I've verif
*All,*
The Apache Jenkins job to build release artifacts for Hadoop 2 is ready (in
its first incarnation). The job URL is:
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
I hope this will make moot all concerns about user accounts and about the
hardware ownership being used to
I agree on not auto-signing (the script does not do it, on purpose).
I was referring to deploying release artifact JARs.
OK, then we are done then.
Thanks.
On Thu, Jan 30, 2014 at 5:02 PM, Roman Shaposhnik wrote:
> On Thu, Jan 30, 2014 at 4:43 PM, Alejandro Abdelnur
> wrote:
> &
[Cross-posting with https://issues.apache.org/jira/browse/HADOOP-10313]
OK, we have:
* A script, create-release.sh, that creates release artifacts
* An Apache Jenkins job that runs the script and produces the artifacts in
Apache CI machines, thanks Yahoo! (or shouldn't I say that?)
The Apache Je
2014 at 9:24 PM, Alejandro Abdelnur wrote:
>
> On Wed, Jan 29, 2014 at 5:38 PM, Suresh Srinivas
> wrote:
>
>> Have you
>> looked at Oozie and are you going to open a jira to change that as well?
>>
>
> Excuse me, what are we taking about here?
>
> The
On Wed, Jan 29, 2014 at 5:38 PM, Suresh Srinivas wrote:
> Have you
> looked at Oozie and are you going to open a jira to change that as well?
>
Excuse me, what are we taking about here?
The only references to Cloudera in Oozie source are in the Apache Oozie
site branch (https://svn.apache.org/re
yeah, Apache Jenkins I've meant
On Wed, Jan 29, 2014 at 4:30 PM, Stack wrote:
> On Wed, Jan 29, 2014 at 4:09 PM, Alejandro Abdelnur >wrote:
>
> > IMO we should't be distributing binaries. And if we do so,they should be
> > built by a Jenkins job.
> >
&
IMO we should't be distributing binaries. And if we do so,they should be
built by a Jenkins job.
Thanks.
On Wed, Jan 29, 2014 at 3:33 PM, Stack wrote:
> On Wed, Jan 29, 2014 at 3:01 PM, Stack wrote:
>
> > What do others think? See here if you do not have access:
> > http://goo.gl/j05wkf
> >
Alejandro Abdelnur created HDFS-5787:
Summary: client Exception when in safemode does not have cause
populated
Key: HDFS-5787
URL: https://issues.apache.org/jira/browse/HDFS-5787
Project: Hadoop
Alejandro Abdelnur created HDFS-5703:
Summary: Add support for HTTPS and swebhdfs to HttpFS
Key: HDFS-5703
URL: https://issues.apache.org/jira/browse/HDFS-5703
Project: Hadoop HDFS
Issue
Sound goods, just a little impedance between what seem to be 2 conflicting
goals:
* what features we target for each release
* train releases
If we want to do train releases at fixed times, then if a feature is not
ready, it catches the next train, no delays of the train because of a
feature. If
Cheers.
Alejandro
Commits in branch-2.2 that I'd like them to be in the 2.2.1 release:
The ones prefixed with '*' technically are not bugs.
YARN-1284. LCE: Race condition leaves dangling cgroups entries for killed
The following is happening in builds for MAPREDUCE and YARN patches.
I've seen the failures in hadoop5 and hadoop7 machines. I've increased
Maven memory to 1GB (export MAVEN_OPTS="-Xmx1024m" in the jenkins
jobs) but still some failures persist:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Buil
new Web UI allows easy migration to any JSON-based APIs
> whenever they land in the trunk.
>
> Thanks,
> Haohui
>
>
> On Mon, Oct 28, 2013 at 5:13 PM, Alejandro Abdelnur wrote:
>
>> Isn't using JMX to expose JSON for the web UI misusing JMX?
>>
>> I wou
tand correctly, that is the exact approach that the new web UI
> is taking. The new web UI takes the output from JMX and renders them as
> HTML at the client side.
>
> ~Haohui
>
>
> On Mon, Oct 28, 2013 at 4:18 PM, Alejandro Abdelnur >wrote:
>
> > Haohui,
> >
&
; the old UI.
>
> This is a good point. Since all information are available through JMX, the
> easiest way to approach it is to write some scripts using Node.js. The
> architecture of the new Web UIs is ready for this.
>
>
> On Mon, Oct 28, 2013 at 3:57 PM, Alejandro Abdelnur
Producing JSON would be great. Agree with Colin that we should leave for
now the current JSP based web ui.
thx
On Mon, Oct 28, 2013 at 11:16 AM, Colin McCabe wrote:
> This is a really interesting project, Haohui. I think it will make
> our web UI much nicer.
>
> I have a few concerns about rem
Alejandro Abdelnur created HDFS-5328:
Summary: MiniDFSCluster times out at startup
Key: HDFS-5328
URL: https://issues.apache.org/jira/browse/HDFS-5328
Project: Hadoop HDFS
Issue Type
+1
* downloaded source tarball
* verified MD5
* verified signature
* verified CHANGES.txt files, release # and date
* run 'mvn apache-rat:check' successfully
* built distribution
* setup speudo cluster
* started HDFS/YARN
* run some HTTFS tests
* run a couple of MR examples
* run a few tests using
Arun,
Does this mean that you want to skip a beta release and go straight to GA
with the next release?
thx
On Tue, Oct 1, 2013 at 4:15 PM, Arun C Murthy wrote:
> Guys,
>
> I took a look at the content in 2.1.2-beta so far, other than the
> critical fixes such as HADOOP-9984 (symlinks) and fe
ping
On Tue, Sep 24, 2013 at 2:36 AM, Alejandro Abdelnur wrote:
> Vote for the 2.1.1-beta release is closing tonight, while we had quite a
> few +1s, it seems we need to address the following before doing a release:
>
> symlink discussion: get a concrete and explicit understandin
Vote for the 2.1.1-beta release is closing tonight, while we had quite a
few +1s, it seems we need to address the following before doing a release:
symlink discussion: get a concrete and explicit understanding on what we
will do and in what release(s).
Also, the following JIRAs seem nasty enough
Are we doing a new RC for 2.1.1-beta?
On Mon, Sep 23, 2013 at 9:04 PM, Vinod Kumar Vavilapalli wrote:
> Correct me if I am wrong, but FWIU, we already released a beta with the
> same symlink issues. Given 2.1.1 is just another beta, I believe we can go
> ahead with it and resolve the issues in
A side note on the protobuf versions, you can have a client and a server
using different versions of protobuf, that works and it works well. What
you cannot do is compile with protoc version X and run using the JAR from
version Y.
On Thu, Sep 19, 2013 at 2:11 AM, J. Rottinghuis wrote:
> However
On Wed, Sep 18, 2013 at 12:03 AM, Karthik Kambatla wrote:
> Not sure if this should be a blocker for 2.1.1, but filed HADOOP-9976 to
> have a single version of avro.
>
>
It depends if there is a known and non-workaroundable issue at runtime
because of this. If not I wouldn't say it is a blocker.
On Wed, Sep 18, 2013 at 11:29 AM, Steve Loughran wrote:
> I'm reluctant for this as while delaying the release, because we are going
> to find problems all the way up the stack -which will require a
> choreographed set of changes. Given the grief of the protbuf update, I
> don't want to go near th
Thanks Arun.
+1
* Downloaded source tarball.
* Verified MD5
* Verified signature
* run apache-rat:check ok after minor tweak (see NIT1 below)
* checked CHANGES.txt headers (see NIT2 below)
* built DIST from source
* verified hadoop version of Hadoop JARs
* configured pseudo cluster
* tested HttpF
It seems a commit of native code in YARN has triggered a native build in
HDFS and things are failing.
-- Forwarded message --
From: Apache Jenkins Server
Date: Mon, Sep 16, 2013 at 1:34 PM
Subject: Hadoop-Hdfs-trunk - Build # 1524 - Still Failing
To: hdfs-dev@hadoop.apache.org
Alejandro Abdelnur created HDFS-5161:
Summary: MiniYARNCluster web ui does not work properly
Key: HDFS-5161
URL: https://issues.apache.org/jira/browse/HDFS-5161
Project: Hadoop HDFS
Alejandro Abdelnur created HDFS-5160:
Summary: MiniDFSCluster webui does not work
Key: HDFS-5160
URL: https://issues.apache.org/jira/browse/HDFS-5160
Project: Hadoop HDFS
Issue Type: Bug
+1
Downloaded source tarball
Verified MD5
Verified Signature
Run apache-rat:check
Did a dist build
Started pseudo cluster
Run a couple of MR examples
Tested HttpFS
On Thu, Aug 15, 2013 at 10:29 PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candidate (rc1) for hadoop-2.0.6
release and upload rc1
> right now.
>
> Please let me know if you feel like we need start doing the license for the
> releasenotes in this release.
>
> Thanks,
> Cos
>
> On Wed, Aug 14, 2013 at 10:40AM, Alejandro Abdelnur wrote:
> > OK:
> > * verified MD
forgot to add: A big thanks to Rajiv and Giri for helping out with the
changes in the Jenkins boxes.
On Wed, Aug 14, 2013 at 4:03 PM, Alejandro Abdelnur wrote:
> Following up on this.
>
> HADOOP-9845 & HADOOP-9872 have been committed
> to trunk/branch-2/branch-2.1-beta/b
Following up on this.
HADOOP-9845 & HADOOP-9872 have been committed
to trunk/branch-2/branch-2.1-beta/branch-2.1.0-beta.
All Hadoop developers must install protoc 2.5.0 in their development
machines for the build to run.
All Hadoop jenkins boxes are using protoc 2.5.0
The BUILDING.txt file has
test-patch came back.
I'll commit to trunk and all "2" branches.
Once done I'll send an email indicating new protoc is required for
development.
Thanks.
On Wed, Aug 14, 2013 at 10:51 AM, Alejandro Abdelnur wrote:
> I've filed https://issues.apache.org/jira/browse/
On Tue, Aug 13, 2013 at 1:09 PM, Alejandro Abdelnur wrote:
>
> There is no indication that protoc 2.5.0 is breaking anything.
>
> Hadoop-trunk builds have been failing way before 1/2 way with:
>
> ---
>
>
> [ERROR] Failed to execute goal
> org.apache.maven
OK:
* verified MD5
* verified signature
* expanded source tar and did a build
* configured pseudo cluster and run a couple of example MR jobs
* did a few HTTP calls to HTTFS
NOT OK:
* CHANGES.txt files have 2.0.6 as UNRELEASED, they should have the date the
RC vote ends
* 'mvn apache-rat:check' fa
2, 2013 at 8:35 PM, Alejandro Abdelnur wrote:
> Jenkins is running a full test run on trunk using protoc 2.5.0.
>
> https://builds.apache.org/job/Hadoop-trunk/480
>
> And it seems go be going just fine.
>
> If everything looks OK, I'm planing to backport HADOOP-9845 to
lures do the protoc mismatch.
Thanks.
Alejandro
On Mon, Aug 12, 2013 at 5:53 PM, Alejandro Abdelnur wrote:
> shooting to get it i n for 2.1.0.
>
> at moment is in trunk till the nightly finishes. then we'll decide
>
> in the mean time, you can have multiple versions install
gt; I did not get definite impression there is.
> If not it could be a pretty big disruption.
>
> Thanks,
> --Konst
>
>
>
> On Mon, Aug 12, 2013 at 3:19 PM, Alejandro Abdelnur wrote:
>
>> I've just committed HADOOP-9845 to trunk (only trunk at the moment).
>
.
On Mon, Aug 12, 2013 at 2:57 PM, Alejandro Abdelnur wrote:
> About to commit HADOOP-9845 to trunk, in 5 mins. This will make trunk use
> protoc 2.5.0.
>
> thx
>
>
> On Mon, Aug 12, 2013 at 11:47 AM, Giridharan Kesavan <
> gkesa...@hortonworks.com> wrote:
>
>&g
x 2.0 branch builds as well.
> Thoughts?
>
> -Giri
>
>
> On Mon, Aug 12, 2013 at 11:37 AM, Alejandro Abdelnur >wrote:
>
> > Giri,
> >
> > first of all, thanks for installing protoc 2.5.0.
> >
> > I didn't know we were installing them as the
is upgraded from 2.4 to 2.5. 2.5 is in the default path.
> If we still need 2.4 I may have to install it. Let me know
>
> -Giri
>
>
> On Sat, Aug 10, 2013 at 7:01 AM, Alejandro Abdelnur >wrote:
>
> > thanks giri, how do we set 2.4 or 2.5., what is the path to
> On Fri, Aug 9, 2013 at 10:56 PM, Giridharan Kesavan <
> gkesa...@hortonworks.com> wrote:
>
>> Alejandro,
>>
>> I'm upgrading protobuf on slaves hadoop1-hadoop9.
>>
>> -Giri
>>
>>
>> On Fri, Aug 9, 2013 at 1:15 PM, Alejandro
pinging again, I need help from somebody with sudo access to the hadoop
jenkins boxes to do this or to get sudo access for a couple of hours to set
up myself.
Please!!!
thx
On Thu, Aug 8, 2013 at 2:29 PM, Alejandro Abdelnur wrote:
> To move forward with this we need protoc 2.5.0 in the apa
Sent: Thursday, August 8, 2013 1:59 AM
> > Subject: Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845
> >
> >
> > Hi,
> >
> > About Hadoop, Harsh is dealing with this problem in HADOOP-9346.
> > For more detail, please see the JIRA
I' like to upgrade to protobuf 2.5.0 for the 2.1.0 release.
As mentioned in HADOOP-9845, Protobuf 2.5 has significant benefits to
justify the upgrade.
Doing the upgrade now, with the first beta, will make things easier for
downstream projects (like HBase) using protobuf and adopting Hadoop 2. If
Thanks Arun,
+1
* verified MD5 & signature of source tarball.
* built from source tarball
* run apache-rat:check on source
* installed pseudo cluster (unsecure)
* test httpfs
* run pi example
* run unmanaged AM application
Minor NITs (in case we do a new RC):
* remove 2.1.1.-beta section from a
to mention in the release notes the API changes and behavior changes that
YARN-918 and YARN-701 will bring into the next beta or GA release.
thx
On Wed, Jul 17, 2013 at 4:14 PM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote:
>
> On Jul 17, 2013, at 1:04 PM, Alejandro Abdeln
Vinod,
Thanks for reviving this thread.
The current blockers are:
https://issues.apache.org/jira/issues/?jql=project%20in%20(hadoop%2C%20mapreduce%2C%20hdfs%2C%20yarn)%20and%20status%20in%20(open%2C%20'patch%20available')%20and%20priority%20%3D%20blocker%20and%20%22Target%20Version%2Fs%22%20%3D%
20, 2013, at 2:40 PM, Arun C Murthy wrote:
>
> > I think I've shared this before, but here you go again…
> >
> > http://s.apache.org/hadoop-2.1.0-beta-blockers
> >
> > At this point, HADOOP-9421 seems like the most important.
> >
> > thanks,
> >
1 - 100 of 200 matches
Mail list logo
