.
~Haohui
On Fri, Apr 4, 2014 at 2:37 PM, Alejandro Abdelnur t...@cloudera.com
wrote:
Haohui,
Is the idea to compile/test with JDK7 and recommend it for runtime and
stop
there? Or to start using JDK7 API stuff as well? If the later is the
case,
then backporting stuff to branch-2 may
Alejandro Abdelnur created HADOOP-10432:
---
Summary: Refactor SSLFactory to expose static method to determine
HostnameVerifier
Key: HADOOP-10432
URL: https://issues.apache.org/jira/browse/HADOOP-10432
Alejandro Abdelnur created HADOOP-10433:
---
Summary: Key Management Server base on KeyProvider API
Key: HADOOP-10433
URL: https://issues.apache.org/jira/browse/HADOOP-10433
Project: Hadoop Common
Alejandro Abdelnur created HADOOP-10427:
---
Summary: KeyProvider implementations should be thread safe
Key: HADOOP-10427
URL: https://issues.apache.org/jira/browse/HADOOP-10427
Project: Hadoop
Alejandro Abdelnur created HADOOP-10428:
---
Summary: JavaKeyStoreProvider should accept keystore password
via configuration falling back to ENV VAR
Key: HADOOP-10428
URL: https://issues.apache.org/jira
Alejandro Abdelnur created HADOOP-10429:
---
Summary: KeyStores should have methods to generate the materials
themselves, KeyShell should use them
Key: HADOOP-10429
URL: https://issues.apache.org/jira/browse
Alejandro Abdelnur created HADOOP-10430:
---
Summary: KeyProvider Metadata should have an optional label, there
should be a method to retrieve the metadata from all keys
Key: HADOOP-10430
URL: https
Alejandro Abdelnur created HADOOP-10431:
---
Summary: Change visibility of KeyStore KeyVersion/Metadata/Options
constructor and methods to public
Key: HADOOP-10431
URL: https://issues.apache.org/jira/browse
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
take 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 t...@cloudera.com wrote:
Hi Vinod,
Nothing confidential,
* With umanaged AMs
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 ste...@hortonworks.com wrote:
On 6 February 2014 17:07, Alejandro Abdelnur t...@cloudera.com wrote
will merge it to branch-2.3 tomorrow PST if no one disagrees.
On Tue, Feb 4, 2014 at 5:03 PM, Alejandro Abdelnur
t...@cloudera.com
wrote:
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
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, Alejandro Abdelnur t...@cloudera.com wrote:
Thanks Robert,
All,
So
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
*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
Alejandro Abdelnur created HADOOP-10313:
---
Summary: Script and jenkins job to produce Hadoop release artifacts
Key: HADOOP-10313
URL: https://issues.apache.org/jira/browse/HADOOP-10313
Project
[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
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 r...@apache.org wrote:
On Thu, Jan 30, 2014 at 4:43 PM, Alejandro Abdelnur t
Alejandro Abdelnur created HADOOP-10235:
---
Summary: Hadoop tarball has 2 versions of stax-api JARs
Key: HADOOP-10235
URL: https://issues.apache.org/jira/browse/HADOOP-10235
Project: Hadoop Common
too early to confirm which APIs can be marked
@Stable. How about not doing this until security is ready and refactoring
duplicate code is done? At that time, we should have a clearer picture
about it.
Thanks,
Zhijie
On Mon, Jan 6, 2014 at 3:02 PM, Alejandro Abdelnur t...@cloudera.com
wrote
This is great news. A few things to consider before doing the merge:
1* The merge must be done in trunk first (then, ideally, from trunk into
branch-2)
2* The last update of YARN-321 was done in NOV10, this was done from
branch-2 (that seems a NIT as it should be against trunk)
3* IMO, until we
Chris,
I'm already on it.
Thanks.
On Fri, Dec 6, 2013 at 9:49 AM, Chris Nauroth cnaur...@hortonworks.comwrote:
+1 for the idea. The branch committership clause was added for exactly
this kind of scenario.
From the phrasing in the bylaws, it looks like we'll need assistance from
PMC to
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
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:
+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
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 a...@hortonworks.com 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
Congratulations
On Tue, Oct 1, 2013 at 8:04 PM, Mattmann, Chris A (398J)
chris.a.mattm...@jpl.nasa.gov wrote:
That is awesome!
Congrats dudes this is great!! Please consider submitting an expanded
version of the paper to J. Big Data from Springer:
http://journalofbigdata.com/
As
ping
On Tue, Sep 24, 2013 at 2:36 AM, Alejandro Abdelnur t...@cloudera.comwrote:
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
Are we doing a new RC for 2.1.1-beta?
On Mon, Sep 23, 2013 at 9:04 PM, Vinod Kumar Vavilapalli vino...@apache.org
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
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
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
On Wed, Sep 18, 2013 at 11:29 AM, Steve Loughran ste...@hortonworks.comwrote:
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
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
+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 c...@apache.org wrote:
All,
I have created a release candidate (rc1) for
Alejandro Abdelnur created HADOOP-9876:
--
Summary: Take advantage of protobuf 2.5.0 new features for
increased performance
Key: HADOOP-9876
URL: https://issues.apache.org/jira/browse/HADOOP-9876
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 MD5
* verified signature
* expanded source tar and did a build
Alejandro Abdelnur created HADOOP-9872:
--
Summary: Improve protoc version handling and detection
Key: HADOOP-9872
URL: https://issues.apache.org/jira/browse/HADOOP-9872
Project: Hadoop Common
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'
, Alejandro Abdelnur t...@cloudera.comwrote:
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.plugins:maven-surefire-plugin:2.12.3:test (default-test
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 t...@cloudera.comwrote:
I've filed https://issues.apache.org/jira/browse/HADOOP-9872
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
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 t...@cloudera.comwrote:
Following up on this.
HADOOP-9845 HADOOP-9872 have been committed
to trunk/branch-2/branch-2.1-beta/branch-2.1.0
, Alejandro Abdelnur t...@cloudera.comwrote:
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 the
2.1.0-beta branch midday PST
.
By tomorrow we should have things mostly sorted out.
Thanks
On Tue, Aug 13, 2013 at 3:29 PM, Steve Loughran ste...@hortonworks.comwrote:
On 13 August 2013 13:09, Alejandro Abdelnur t...@cloudera.com wrote:
There is no indication that protoc 2.5.0 is breaking anything.
clearly
. 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 t...@cloudera.com
wrote:
thanks giri, how do we set 2.4 or 2.5., what is the path to both so we
can
use and env to set it in the jobs
as well.
Thoughts?
-Giri
On Mon, Aug 12, 2013 at 11:37 AM, Alejandro Abdelnur t...@cloudera.com
wrote:
Giri,
first of all, thanks for installing protoc 2.5.0.
I didn't know we were installing them as the only version and not driven
by
env/path settings.
Now we have a bit
12, 2013 at 2:57 PM, Alejandro Abdelnur t...@cloudera.comwrote:
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:
I can take care of re-installing 2.4
Alejandro Abdelnur created HADOOP-9866:
--
Summary: convert hadoop-auth testcases requiring kerberos to use
minikdc
Key: HADOOP-9866
URL: https://issues.apache.org/jira/browse/HADOOP-9866
Project
do the protoc mismatch.
Thanks.
Alejandro
On Mon, Aug 12, 2013 at 5:53 PM, Alejandro Abdelnur t...@cloudera.comwrote:
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 installed in diff dirs
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 Abdelnur t...@cloudera.comwrote:
pinging again, I need help from somebody with sudo access
Alejandro Abdelnur created HADOOP-9859:
--
Summary: remove TABs from source
Key: HADOOP-9859
URL: https://issues.apache.org/jira/browse/HADOOP-9859
Project: Hadoop Common
Issue Type: Bug
:
On Fri, Aug 9, 2013 at 1:15 PM, Alejandro Abdelnur t...@cloudera.com
wrote:
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.
Have you asked on builds@ or filed an INFRA Jira issue
, Alejandro Abdelnur t...@cloudera.com
wrote:
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
...@yahoo-inc.com; Kai Zheng; Alejandro Abdelnur
Subject: Re: [DISCUSS] Hadoop SSO/Token Server Components
It seems to me that we can have the best of both worlds here...it's all
about the scoping.
If we were to reframe the immediate scope to the lowest common
denominator of what is needed
branch.
http://mail-archives.apache.org/mod_mbox/hadoop-general/201308.mbox/%3CCACO5Y4we4d8knB_xU3a=hr2gbeqo5m3vau+inba0li1i9e2...@mail.gmail.com%3E
Chris Nauroth
Hortonworks
http://hortonworks.com/
On Tue, Aug 6, 2013 at 1:04 PM, Alejandro Abdelnur t...@cloudera.com
wrote:
Larry
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
done.
thx
On Tue, Jul 30, 2013 at 11:02 AM, Vinod Kumar Vavilapalli
vino...@hortonworks.com wrote:
Done for HADOOP, YARN and MAPREDUCE.
Can somebody on HDFS do it too?
Thanks,
+Vinod
On Jul 30, 2013, at 10:31 AM, Chris Nauroth wrote:
I just documented a patch in the 2.1.1-beta
Larry, all,
Still is not clear to me what is the end state we are aiming for, or that
we even agree on that.
IMO, Instead trying to agree what to do, we should first agree on the
final state, then we see what should be changed to there there, then we see
how we change things to get there.
The
requests with non-normalized capabilities. (ywskycn via tucu)
On Tue, Jul 9, 2013 at 10:54 AM, Arun C Murthy a...@hortonworks.com wrote:
On Jul 2, 2013, at 3:54 PM, Alejandro Abdelnur t...@cloudera.com wrote:
We need clarification on this then.
I was under
metrics. (sandyr via tucu)
On Wed, Jul 10, 2013 at 12:58 PM, Arun C Murthy a...@hortonworks.com wrote:
Sounds good. I'll re-create branch-2.1.0-beta from branch-2.1-beta when
the last 2 blockers are in.
thanks,
Arun
On Jul 10, 2013, at 10:56 AM, Alejandro Abdelnur t...@cloudera.com
wrote
[moving bigtop to bcc]
Tim,
Except from HADOOP-9680 which has significant code changes and some false
changes (which I did not go thru), all other changes seem OK.
* Have you had a change to run ALL Hadoop testcases with them applied to
make sure there are not regression?
* Have you look at
webhdfs under load?
that would definitely help
thx
Alejandro
(phone typing)
On Jul 8, 2013, at 17:43, Suresh Srinivas sur...@hortonworks.com wrote:
Isn't Jetty used by WebHDFS? Given that, Jetty performance is still
important.
On Mon, Jul 8, 2013 at 2:06 PM, Alejandro Abdelnur t
Leaving JIRAs and design docs aside, my recollection from the f2f lounge
discussion could be summarized as:
--
1* Decouple users-services authentication from (intra) services-services
authentication.
The main motivation for this is to get pluggable authentication and
integrated SSO
Hi Lulynn,
I've commented in the JIRA, now that I see your email that gives me a bit
more of context on what you are trying to do.
If I understand correctly, you are trying to use this outside of Hadoop. If
that is the case you should set the PREFIX.kerberos.name.rules=DEFAULT
(or a custom
, Alejandro Abdelnur wrote:
Thanks Suresh, didn't know that, will do.
On Fri, Jun 21, 2013 at 9:48 AM, Suresh Srinivas sur...@hortonworks.com
wrote:
I have added in to HDFS, HADOOP, MAPREDUCE projects. Can someone add it
for
YARN?
On Fri, Jun 21, 2013 at 9:35 AM, Alejandro Abdelnur t
why not just add a precommit hook in svn to reject commits with CRLF?
On Mon, Jul 1, 2013 at 10:51 AM, Raja Aluri r...@cmbasics.com wrote:
I added a couple of links that discusses 'line endings' when I added
.gitattributes in this JIRA.
PM, Arun C Murthy a...@hortonworks.com 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,
Arun
On Jun 20, 2013, at 8:31 AM, Alejandro Abdelnur t
When Arun created branch-2.1-beta he stated:
The expectation is that 2.2.0 will be limited to content in
branch-2.1-beta
and we stick to stabilizing it henceforth (I've deliberately not created
2.2.0
fix-version on jira yet).
I working/committing some JIRAs that I'm putting in branch-2
Thanks Suresh, didn't know that, will do.
On Fri, Jun 21, 2013 at 9:48 AM, Suresh Srinivas sur...@hortonworks.comwrote:
I have added in to HDFS, HADOOP, MAPREDUCE projects. Can someone add it for
YARN?
On Fri, Jun 21, 2013 at 9:35 AM, Alejandro Abdelnur t...@cloudera.com
wrote:
When
Arun,
It seems there are still a few things to iron out before getting 2.1 out of
the door.
As RM for the release, would you mind sharing the current state of things
and your estimate on when it could happen?
Thanks.
On Wed, Jun 19, 2013 at 4:29 PM, Roman Shaposhnik r...@apache.org wrote:
This sounds great,
Is this restricted to the Hadoop project itself or the intention is to
cover the whole Hadoop ecosystem? If the later, how are you planning to
engage and sync up with the different projects?
Thanks.
On Thu, Jun 20, 2013 at 9:45 AM, Larry McCay lmc...@hortonworks.com wrote:
, 2013, at 8:19 AM, Alejandro Abdelnur wrote:
Of the JIRAs in my laundry list for 2.1 the ones I would really want in
are
YARN-752, MAPREDUCE-5171 YARN-787.
I agree YARN-787 needs to go in ASAP is a blocker - I'm looking at it
right now.
I committed YARN-787. Thanks.
Arun
? This is related to YARN-787.
thanks,
Arun
On Jun 16, 2013, at 8:56 AM, Alejandro Abdelnur wrote:
Thanks Arun, I'll take care of committing YARN-752 and MAPREDUCE-5171
around noon today (SUN noon PST).
What is your take on YARN-791 MAPREDUCE-5130?
On Sun, Jun 16, 2013 at 7:02 AM, Arun C
Arun,
This sounds great. Following is the list of JIRAs I'd like to get in. Note
that the are ready or almost ready, my estimate is that they can be taken
care of in a couple of day.
Thanks.
* YARN-752: In AMRMClient, automatically add corresponding rack requests
for requested nodes
impact:
+1 RC2. Verified MD5 signature, checked CHANGES.txt files, built,
configured pseudo cluster, run a couple of sample jobs, tested HTTPFS.
On Mon, Jun 3, 2013 at 12:51 PM, Konstantin Boudnik c...@apache.org wrote:
I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha.
The
would be happy to fix it if this seems to be a problem.
Thanks,
Cos
On Sat, Jun 01, 2013 at 08:04PM, Alejandro Abdelnur wrote:
On RC1, verified MD5 signature, built, configured pseudo cluster, run a
couple of sample jobs, tested HTTPFS.
CHANGES.txt files contents are correct now. Still
:27PM, Alejandro Abdelnur wrote:
Verified MD5 signature, built, configured pseudo cluster, run a
couple of
sample jobs, tested HTTPFS.
Still, something seems odd.
The HDFS CHANGES.txt has the following entry under 2.0.5-alpha:
HDFS-4646
Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now
(FRI MAY31 1PM PST). Correct?
Thx
On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik c...@apache.org wrote:
Guys,
I will be performing some changes wrt to moving 2.0.4.1 release candidate
to
2.0.5 space. As outline
Verified MD5 signature, built, configured pseudo cluster, run a couple of
sample jobs, tested HTTPFS.
Still, something seems odd.
The HDFS CHANGES.txt has the following entry under 2.0.5-alpha:
HDFS-4646. createNNProxyWithClientProtocol ignores configured timeout
value (Jagane Sundar via
On the version number we use, if it is greater than 2.0.4, I really don't
care. Though I think Konstantin argument that branch-2 is publishing as
2.0.5-SNAPSHOT has some ground (still, it could be argued that they are DEV
JARs so they can be in flux).
On the changes that went into this RC, they
Konstantin, Cos,
As we change from 2.0.4.1 to 2.0.5 you'll need to do the following
housekeeping as you work the new RC.
* rename the svn branch
* update the versions in the POMs
* update the CHANGES.txt in trunk, branch-2 and the release branch
* change the current 2.0.5 version in JIRA to
+1, verified MD5 and signature. Did a full build, started pseudo cluster,
run a few MR jobs, verified httpfs works.
Thanks.
On Sat, May 25, 2013 at 10:01 AM, Sangjin Lee sj...@apache.org wrote:
+1 (non-binding)
Thanks,
Sangjin
On Fri, May 24, 2013 at 8:48 PM, Konstantin Boudnik
+1, verified MD5 and signature. Did a full build, started pseudo cluster,
run a few MR jobs, verified httpfs works.
Thanks.
On Tue, May 28, 2013 at 9:00 AM, Thomas Graves tgra...@yahoo-inc.comwrote:
I've created a release candidate (RC0) for hadoop-0.23.8 that I would like
to release.
+1
On Tue, May 21, 2013 at 2:48 PM, Suresh Srinivas sur...@hortonworks.comwrote:
+1
On Tue, May 21, 2013 at 2:10 PM, Matt Foley ma...@apache.org wrote:
Hi all,
This has been a side topic in several email threads recently. Currently
we
have an ambiguity. We have a tradition in the
Do we need to add YARN-397?
Thanks.
On Wed, May 15, 2013 at 11:23 AM, Karthik Kambatla ka...@cloudera.comwrote:
Hi Arun,
Can we add HADOOP-9517 to the list - having compatibility guidelines should
help us support users and downstream projects better?
Thanks
Karthik
On Wed, May 15,
Andrew,
Or with a twist, why not break/consolidate things as follows?
common API
common IMPL
hdfs CLIENT IMPL
hdfs SERVER IMPL
hdfs TOOLS
other filesystems CLIENT
yarn API
yarn CLIENT IMPL
yarn SERVER IMPL
yarn TOOLS
mapred API
mapred IMPL
mapred TOOLS
IMO, this would help significantly to
, Alejandro Abdelnur wrote:
while trying to commit MAPREDUCE-5113 to branch-2 I've noticed that
the
CHANGES.txt are out of sync. Commit message are on the wrong releases.
I've spent some some time trying to fix it, but I did not find it
straight
forward to do so.
I assume
Alejandro Abdelnur created HADOOP-9471:
--
Summary: hadoop-client wrongfully excludes jetty-util JAR,
breaking webhdfs
Key: HADOOP-9471
URL: https://issues.apache.org/jira/browse/HADOOP-9471
I've comitted HADOOP-9471 to trunk and branch-2 and closed JIRA with
fixedVersion 2.0.5.
If this JIRA makes it to 2.0.4 we need to update CHANGES.txt in
trunk/branch-2 and the fixedVersion in the JIRA.
Thx.
On Tue, Apr 9, 2013 at 8:39 PM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
while trying to commit MAPREDUCE-5113 to branch-2 I've noticed that the
CHANGES.txt are out of sync. Commit message are on the wrong releases.
I've spent some some time trying to fix it, but I did not find it straight
forward to do so.
I assume the same may be true for common, hdfs and yarn.
I
[
https://issues.apache.org/jira/browse/HADOOP-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HADOOP-9342.
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks Thomas. Committed to trunk
[
https://issues.apache.org/jira/browse/HADOOP-9246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur reopened HADOOP-9246:
I think a more correct way of fixing this (realized that while doing the protoc
Alejandro Abdelnur created HADOOP-9304:
--
Summary: remove addition of avro genreated-sources dirs to build
Key: HADOOP-9304
URL: https://issues.apache.org/jira/browse/HADOOP-9304
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-9246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HADOOP-9246.
Resolution: Fixed
arghh, got it, i was missing that. Closing it then.
I guess we
Alejandro Abdelnur created HADOOP-9297:
--
Summary: remove old record IO generation and tests
Key: HADOOP-9297
URL: https://issues.apache.org/jira/browse/HADOOP-9297
Project: Hadoop Common
AFAIK, official release artifacts MUST be source artifacts, binary
artifacts are convenience ones. The vote should be on source artifacts.
Thx
On Fri, Feb 8, 2013 at 8:52 AM, Chris Douglas cdoug...@apache.org wrote:
+1 (binding)
Looks like your key isn't in the file:
[
https://issues.apache.org/jira/browse/HADOOP-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur reopened HADOOP-9253:
Now, when starting the cluster you get on the console
{code}
ulimit -a for user tucu
)
includes the src/ directory, which contains the full Apache sources.
Thanks,
--Matt
On Fri, Feb 8, 2013 at 9:37 AM, Alejandro Abdelnur t...@cloudera.com
wrote:
AFAIK, official release artifacts MUST be source artifacts, binary
artifacts are convenience ones. The vote should be on source
This seems to be used only in tests in common and in a standalone class in
streaming tests.
What is the purpose of these classes as they don't seem to be used in the
any of the source that ends up in Hadoop?
hadoop-common-project/hadoop-common/src/test/ddl/buffer.jr
+1. Downloaded SRC, verified MD5 and signature, did a full build,
configured, started up HDFS, YARN, HTTPS, run a a couple of example MR
jobs, tested HTTPS access to HDFS.
Thanks for driving this release Arun.
On Thu, Feb 7, 2013 at 7:33 AM, Robert Evans ev...@yahoo-inc.com wrote:
I
101 - 200 of 319 matches
Mail list logo
