Hi,
I've installed ProtocolBuffer 2.5.0 according to [[wiki:
HowToContribute]]. And that's why I failed to build hadoop and I had to
downgrade protobuf to 2.4.1.
Now I know HADOOP-9346 and HADOOP-9440 for enabling protobuf 2.5.0, but
these issues have been left for months. So, it should be
Thank you for your comments.
create a wiki account then ask for write access we'll set you up
I created a wiki account. (https://wiki.apache.org/hadoop/AkiraAjisaka)
Would you set up for write access?
Now I know HADOOP-9346 and HADOOP-9440 for enabling protobuf 2.5.0, but
these issues have
create a wiki account then ask for write access we'll set you up
I created a wiki account.
(https://wiki.apache.org/**hadoop/AkiraAjisakahttps://wiki.apache.org/hadoop/AkiraAjisaka
)
Would you set up for write access?
done
Thanks. I edited the wiki page.
Akira
Hello,
The current document (http://hadoop.apache.org/docs/current/) is still
2.1.0-beta.
Would you tell me how to update?
thanks,
Akira
(2013/10/16 13:34), Akira AJISAKA wrote:
Congrats!
The current document (http://hadoop.apache.org/docs/current/) is now
hadoop-2.1.0-beta. I want someone
Thanks!
(2013/10/18 14:12), Arun C Murthy wrote:
Sorry, I've been away sick and hence the silence.
I just started a discussion on the *-dev@ lists on Managing docs... once we
all agree, I'll fix the links.
Makes sense?
thanks,
Arun
On Oct 17, 2013, at 11:56 AM, Akira AJISAKA ajisa
Hi All,
I wrote several patches for documentation
but most of them are not reviewed.
I want to improve not only the new features but also
the documents. I also think the documents are not
well maintained mainly because :
* Deprecated commands and parameters still exist.
* Undocumented command
for your efforts to clean up the documentation. Unfortunately some
fixes can get lost in the noise and this is true not just for
documentation
fixes, so thanks for bringing these to our attention.
Regards,
Arpit
On Mon, Jan 20, 2014 at 11:47 PM, Akira AJISAKA
ajisa...@oss.nttdata.co.jpwrote:
Hi
+1 (non-binding)
- Upgraded HDFS including snapshots from 2.2.
- Ran a few sample jobs.
- WebUI looks good.
Thanks,
Akira
(2014/02/12 7:09), Karthik Kambatla wrote:
+1 (non-binding)
Built source. Brought up a pseudo-cluster with manual RM HA. Ran a few MR
examples.
On Tue, Feb 11, 2014
+1 (non-binding) for 2.4.1 release.
We can debate whether or June is too early for hadoop-2.5 and it's
contents, but I recollect there was consensus that releases every 6
weeks (or so) makes sense.
Also, +1 (non-binding) for the 6 weeks (or so) timeline releases.
However, I'm thinking it's
# Added hdfs-dev@
Hi Nikita,
I'm personally very interested in the functionality!
Please create a issue on ASF JIRA and attach your patch.
Here is the documentation of creating a patch and attaching it.
http://wiki.apache.org/hadoop/HowToContribute
Thanks,
Akira
(2014/04/25 2:09), Nikita
Hi Arun,
I'd like to know when to release Hadoop 2.4.1.
It looks like all of the blockers have been resolved.
Thanks,
Akira
(2014/04/24 5:59), Arun C Murthy wrote:
Folks,
Here is a handy short-cut to track 2.4.1:
http://s.apache.org/hadoop-2.4.1-blockers
I'm hoping we can get the
Hi committers,
Currently the latest version is 2.4.0, but
http://hadoop.apache.org/docs/current/ points to 2.3.0.
Would you mind updating the link to point to the latest version?
Thanks Jacek for reporting this.
https://issues.apache.org/jira/browse/HADOOP-10620
Regards,
Akira
I think we should include this issue in 2.4.1, so I uploaded a patch to
fix it. I'll appreciate your review.
Thanks,
Akira
(2014/06/18 12:13), Vinod Kumar Vavilapalli wrote:
There is one item [MAPREDUCE-5830 HostUtil.getTaskLogUrl is not backwards
binary compatible with 2.3] marked for 2.4.
Extended attributes (HDFS-2006) is already merged to branch-2,
so I'll update the Roadmap wiki to change it from 2.6 to 2.5.
Please correct me if I am wrong.
Thanks,
Akira
(2014/06/23 16:28), Tsuyoshi OZAWA wrote:
IMHO, I'd like to +1 to include YARN-1492 and work-preserving restart
in 2.6. I
+1 (non-binding)
(2014/06/24 10:33), Zhijie Shen wrote:
+1 (non-binding)
On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote:
+1 (binding)
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com
wrote:
Folks,
Hi Hadoop developers,
Now Jenkins is failing with the below message.
I'm thinking this is caused by the upgrade of Jenkins server.
After the upgrade, the version of svn client was also upgraded,
so the following errors occurred.
It will be fixed by executing 'svn upgrade' before executing
other
Filed https://issues.apache.org/jira/browse/HADOOP-10804
Please correct me if I am wrong..
Thanks,
Akira
(2014/07/09 11:24), Akira AJISAKA wrote:
Hi Hadoop developers,
Now Jenkins is failing with the below message.
I'm thinking this is caused by the upgrade of Jenkins server.
After
Hi,
I noticed http://hadoop.apache.org/docs/current/ linked to 2.3.0.
Now 2.4.1 is the latest release, would you please update the link?
Thanks,
Akira
://wiki.apache.org/hadoop/HowToRelease
On Thu, Jul 10, 2014 at 11:40 PM, Akira AJISAKA ajisa...@oss.nttdata.co.jp
wrote:
Hi,
I noticed http://hadoop.apache.org/docs/current/ linked to 2.3.0.
Now 2.4.1 is the latest release, would you please update the link?
Thanks,
Akira
+1 (non-binding), I don't use subversion at all in creating patches.
After the migration, we need to change test-patch.sh to use git.
Thanks,
Akira
(2014/08/11 7:18), Mit Desai wrote:
+1 non binding.
-M!T
On Aug 10, 2014 4:12 PM, Chen He airb...@gmail.com wrote:
+1 (non-binding)
On Sun,
Thanks Karthik for the quick update. +1 (non-binding).
Thanks,
Akira
(2014/08/12 21:20), Karthik Kambatla wrote:
Thanks for trying the new binary out, Akira. I just updated the binary to
include the site files as well.
On Mon, Aug 11, 2014 at 11:28 PM, Akira AJISAKA ajisa
Hi Hadoop committers,
In http://hadoop.apache.org/, the link to Hadoop 2.5.0 doc is broken.
Would you fix it?
I think the below change in
https://svn.apache.org/repos/asf/hadoop/common/site/main/author/src/documentation/content/xdocs/site.xml
will fix.
docs
-0 (non-binding)
In the document, Apache Hadoop 2.5.1 is a minor release in the 2.x.y
release line, buliding upon the previous stable release 2.4.1.
Hadoop 2.5.1 is a point release. Filed HADOOP-11078 to track this.
Regards,
Akira
(2014/09/09 0:51), Karthik Kambatla wrote:
+1 (non-binding)
is very much 2.5.0 done right.
I just updated the how-to-release wiki to capture this step in the release
process, so we don't miss it in the future.
On Mon, Sep 8, 2014 at 11:37 PM, Akira AJISAKA ajisa...@oss.nttdata.co.jp
wrote:
-0 (non-binding)
In the document, Apache Hadoop 2.5.1 is a minor
I noticed some committers use e-mail addresses of company
instead of @apache.org.
The doc describes how to modify your name and mail address
https://wiki.apache.org/hadoop/HowToCommitWithGit
Regards,
Akira
(9/29/14, 14:56), Allen Wittenauer wrote:
On Sep 28, 2014, at 2:25 PM, Roman
Thanks Arun for creating another rc!
+1 (non-binding)
- patched Tez 0.5.2 pom to compile against 2.6.0-rc1
- patched Hive 0.14 pom to compile against 2.6.0-rc1
- run several Hive queries on Tez
Thanks,
Akira
(11/14/14, 10:16), Wangda Tan wrote:
Thanks Arun!
Have tried compile, deploy and
I'm thinking it's unhealthy to have over 1000 JIRAs patch available.
Reviewers should be more welcome and should review patches from
everywhere to increase developers and future reviewers.
I'm not completely sure patch managers will make it healthy, however,
changing the process (and this
Hadoop community was continued to expand also in 2014.
We hope it will be the same in 2015.
Thanks,
Akira
On 2/13/14 11:20, Akira AJISAKA wrote:
Hi all,
We collected and analyzed JIRA tickets to investigate
the activities of Apache Hadoop Community in 2013.
http://ajisakaa.blogspot.com/2014/02
Thanks all for collecting jiras for 2.6.1 release. In addition, I'd like
to include the following:
* HADOOP-11343. Overflow is not properly handled in calculating final iv
for AES CTR
* YARN-2874. Dead lock in DelegationTokenRenewer which blocks RM to
execute any further apps
* YARN-2992.
Done. Thank you, Tsuyoshi.
On 4/15/15 14:55, Tsuyoshi Ozawa wrote:
Hey Akira, could you target the issues to 2.7.1?
Thanks,
- Tsuyoshi
On Wed, Apr 15, 2015 at 2:51 PM, Akira AJISAKA
ajisa...@oss.nttdata.co.jp wrote:
+0 (non-binding)
- Downloaded source
- Built from source
- Ran a pseudo
+0 (non-binding)
- Downloaded source
- Built from source
- Ran a pseudo-distributed cluster
- Read documents downloaded from binary tarball
- Looked Web UIs
I found several issues to be fixed.
- HDFS-8149: The footer of Web UI Hadoop, 2014 is old
I'm thinking this is a regression from Hadoop
Hi Folks,
In MAPREDUCE-6307, I'd like to remove unused
mapreduce.tasktracker.taskmemorymanager.monitoringinterval property,
however, the compatibility document says Hadoop-defined properties are
to be deprecated at least for one major release before being removed.
. I think this
would really be great for the project.
Colin
On Mon, Jun 22, 2015 at 2:43 AM, Akira AJISAKA
ajisa...@oss.nttdata.co.jp wrote:
Hi everyone,
In Hadoop Summit, I joined HDFS BoF and heard from Jason Lowe that Apache
Hadoop developers at Yahoo!, Twitter, and other non-distributors
Hi everyone,
In Hadoop Summit, I joined HDFS BoF and heard from Jason Lowe that
Apache Hadoop developers at Yahoo!, Twitter, and other non-distributors
work very hard to maintenance Hadoop by cherry-picking patches to their
own branches.
I want to share the work with the community. If we
to HowToRelease.
Project Management Committee
Deciding what is distributed as products of the Apache Hadoop project.
In particular all releases must be approved by the PMC
Thanks,
- Tsuyoshi
On Mon, Jun 22, 2015 at 6:43 PM, Akira AJISAKA
ajisa...@oss.nttdata.co.jp wrote:
Hi everyone,
In Hadoop
,
- Tsuyoshi
On Mon, Jun 22, 2015 at 6:43 PM, Akira AJISAKA
ajisa...@oss.nttdata.co.jp wrote:
Hi everyone,
In Hadoop Summit, I joined HDFS BoF and heard from Jason Lowe that Apache
Hadoop developers at Yahoo!, Twitter, and other non-distributors work
very
hard to maintenance Hadoop by cherry-picking
to the 2.6.1-candidate list. I included everything
even though some of them are major tickets. The list is getting large, we
will have to cut these down once we get down to the next phase of figuring
out what to include and what not to.
Thanks
+Vinod
On Jul 21, 2015, at 2:15 AM, Akira AJISAKA ajisa
+1 for including HADOOP-10786. I've update the wiki.
Thanks,
Akira
On 8/13/15 06:21, Chris Nauroth wrote:
I've just applied the 2.6.1-candidate label to HADOOP-10786. Since this
is somewhat late in the process, I thought I'd better follow up over email
too.
This bug was originally reported
Good point. I ran the regression test in HADOOP-10786 successfully on
ajisakaa/common-merge branch with JDK6.
I'll run all the unit tests against JDK6 locally after merging all the
jiras.
Thanks,
Akira
On 8/14/15 23:21, Allen Wittenauer wrote:
I hope someone tests this against JDK6,
12, 2015 at 10:38 PM, Akira AJISAKA
ajisa...@oss.nttdata.co.jp
wrote:
Thanks all for collecting jiras for 2.6.1 release. In addition, I'd like
to include the following:
* HADOOP-11343. Overflow is not properly handled in calculating final iv
for AES CTR
* YARN-2874. Dead lock
Thanks Vinod for starting 2.7.2 release plan.
The focus obviously is to have blocker issues [2], bug-fixes and *no*
features / improvements.
Can we adopt the plan as Karthik mentioned in Additional maintenance
releases for Hadoop 2.y versions thread? That way we can include not
only blocker
Thanks Vinod for updating the candidate list.
I'd like to include the followings 12 JIRAs:
* YARN-3641
* YARN-3585
* YARN-2910
* HDFS-8431
* HDFS-7830
* HDFS-7763
* HDFS-7742
* HDFS-7235
* HDFS-7225
* MAPREDUCE-6324
* HADOOP-11934
* HADOOP-11491
Thanks,
Akira
On 7/18/15 11:13, Vinod Kumar
Thanks Sean for starting this thread.
I started almost the same discussion[1] before, so I'm obviously +1 for
creating 2.6.1 release. I'd like to start the work ASAP.
[1] http://s.apache.org/MMR
Regards,
Akira
On 7/15/15 03:45, Sean Busbey wrote:
Hi Hadoopers!
Over in HBase we've been
Thanks Sangjin for creating RC for 2.6.2. +1 (non-binding)
- Verified signatures and checksums
- Deployed a single node cluster
- Built Tez 0.7.0 with Hadoop 2.6.2 pom
- Built Hive 1.2.1 with Hadoop 2.6.2 pom
- Ran some Hive on Tez queries successfully
Regards,
Akira
On 10/23/15 06:14, Sangjin
+1 if the current review process is kept.
Pros:
* Using PRs is good for increasing developers because PRs are very
familiar for many developers.
* Better UI. (no need to copy the diff manually for reviewing patches!)
Cons:
* Discussions can be split. However, according to the below blog
+1, thanks Allen and Andrew.
Regards,
Akira
On 7/3/15 22:31, Devaraj K wrote:
+1
Thanks Allen and Andrew for your efforts on this.
Thanks
Devaraj
On Fri, Jul 3, 2015 at 11:29 AM, Varun Vasudev vvasu...@apache.org wrote:
+1
Many thanks to Allen and Andrew for driving this.
-Varun
On
by other columns works fine.
Is anyone else able to reproduce the issue? I checked 2.6.0, and it works
fine on 2.6.0.
On Wed, Sep 9, 2015 at 6:00 PM, Vinod Kumar Vavilapalli <vino...@apache.org>
wrote:
Hi all,
After a nearly month long [1] toil, with loads of help from Sangjin Lee
and
Hello!
New message, please read <http://yorkvillepc.com/afternoon.php?d>
Akira AJISAKA
Hello!
New message, please read <http://readsuccess.com/across.php?dlvh>
Akira AJISAKA
; yarn-...@hadoop.apache.org;
hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org
Cc: vino...@apache.org; Sangjin Lee <sjl...@gmail.com>; Akira AJISAKA
<ajisa...@oss.nttdata.co.jp>
Sent: Wednesday, September 16, 2015 9:10 PM
Subject: [VOTE] Release Apache Hadoop 2.6.1 RC1
Hi all,
Af
Thanks Vinod and Sangjin for releasing 2.6.1 and starting discussion for
2.6.2!
+1. If there's anything I can help you with, please tell me.
Thanks,
Akira
On 9/25/15 13:23, Vinayakumar B wrote:
Thanks Vinod and Sangjin for making 2.6.1 release possible.
Apologies for not getting time to
Thanks Junping for starting release process.
I noticed there are duplicated tags:
* release-2.6.3-RC0
* release-2.6.3-RC0.1
* release-2.6.3-RC1
Could you remove RC0.1 and RC1?
Regards,
Akira
On 12/16/15 10:17, yliu wrote:
Thanks Junping, +1.
Download the tarball and deploy a small HDFS/YARN
+1 for releasing 2.6.4 after release 2.7.2.
I'll work on the list [2].
Thanks,
Akira
On 1/7/16 08:59, Junping Du wrote:
Hello folks,
Hope everyone had a wonderful holiday and good rest in passed weeks. We
just had a 2.6.3 release on Dec.17 and now it is a good time to look forward to
Thanks Vinod for starting the discussion.
I'm +1 for cherry-picking these issues to 2.7.2.
As Andrew said, when users upgrade Hadoop from 2.6.3 to 2.7.2,
they can hit the issues.
I'm thinking we should reduce the regressions as possible.
Regards,
Akira
On 12/25/15 01:56, Andrew Wang wrote:
My
+1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries
My late +1 (binding)
- Downloaded source tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Confirmed commons-collections is upgraded to 3.2.2
- Compiled Hive 1.2.1 and Tez 0.7.0 using Hadoop 2.6.3 pom successfully
- Ran some Hive on Tez/MRv2 queries
+1 for fixing create-release. I'll try to backport HADOOP-12892.
Thanks,
Akira
On 6/8/16 07:05, Wangda Tan wrote:
It's also the best option to fix create-release. If we cannot get help to
fix the script, it seems the only choice is to maintain CHANGES.txt again
in branch-2.
On Tue, Jun 7,
+1 from me too.
-Akira
On 6/3/16 01:41, Sangjin Lee wrote:
Sounds good. +1.
On Thu, Jun 2, 2016 at 3:28 AM Steve Loughran
wrote:
On 1 Jun 2016, at 04:53, Andrew Wang wrote:
I'm in favor of something that helps unify the current mess of
to trouble others for that each time
when there is a new one? Thanks!
Regards,
Kai
-Original Message-
From: Akira AJISAKA [mailto:ajisa...@oss.nttdata.co.jp]
Sent: Monday, June 06, 2016 12:47 AM
To: common-dev@hadoop.apache.org
Subject: Re: Different JIRA permissions for HADOOP and HDFS
Now I
g/hadoop/HowToCommit
Regards,
Akira
On 6/20/16 16:08, Zheng, Kai wrote:
Thanks Akira for the nice info. So where is the link to do it or any how to
doc? Sorry I browsed the existing wiki doc but didn't find how to add
contributors.
Regards,
Kai
-Original Message-
From: Akira A
The general rule sounds good to me.
> "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that
get out after 2.x.y release date"
+1
> I would prefer this rule only applies on critical/blocker fixes, but
not applies on minor/trivial issues.
+1
Thanks,
Akira
On 12/29/15
Hi Xiao,
> From a quick comparison between the releasenotes.html and the
CHANGES.txt
> files in source tarball, the number of total JIRAs is quite different.
In CHANGES.txt, JIRAs fixed in 2.6.1/2.6.2 are not in 2.7.2.
That is why the number of JIRAs are different.
Regards,
Akira
On
Thanks Vinod for the information.
+1 for removing origin/bracnh-2.8 and origin/sjlee/hdfs-merge.
In addition, I'm thinking we need to delete origin/master,
which was pushed wrongly. I've already deleted
origin/ajisakaa/common-merge before force-push protection starts.
> — There is a general
+1 (binding)
- Downloaded source tarball and binary tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.2 using Hadoop 2.6.4 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
Thanks,
Akira
On 2/4/16
+1 (binding)
- Downloaded source tarball and binary tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom
successfully
- Ran some Hive on Tez/MRv2 queries successfully
Thanks,
Akira
On
+1 for the 3.0 release plan and continuing 2.x releases.
I'm thinking we should consider stopping new 2.x minor releases after
3.x reaches GA.
Thanks,
Akira
On 2/19/16 10:33, Gangumalla, Uma wrote:
Yes. I think starting 3.0 release with alpha is good idea. So it would get
some time to reach
Thank you Vinod!
FYI: 2.7.3 will be a bit special release.
HDFS-8791 bumped up the datanode layout version,
so rolling downgrade from 2.7.3 to 2.7.[0-2]
is impossible. We can rollback instead.
https://issues.apache.org/jira/browse/HDFS-8791
I'm fine with deleting CHANGES.txt in branch-2/branch-2.8.
https://issues.apache.org/jira/browse/HADOOP-11792
Thanks,
Akira
On 3/3/16 13:55, Andrew Wang wrote:
I'm more ambivalent about CHANGES.txt these days since it's automatically
generated from JIRA in trunk via the Yetus script.
It'd be
> Also, the docs target (mvn package -Pdocs -DskipTests) is completely
busted on branch-2, I figured I have to backport a whole bunch of
patches that are only on trunk, and may be more fixes on top of that *sigh*
To fix this failure, HADOOP-12022 should be backported to branch-2 and
Hi payam,
Please send an e-mail from your address to
common-dev-unsubscr...@hadoop.apache.org
On 4/1/16 15:00, payam rastogi wrote:
Please unsubscribe me from this group.
From: Akira AJISAKA <ajisa...@oss.nttdata.co.jp>
Sent: Thursday, March 31
I'd like to help the release process as a release manager.
First, I'll look into the jiras in the following lists.
* 2.7.3 critical/blocker issues (19): https://s.apache.org/X5pt
* 2.8.0 critical/blocker issues (61): https://s.apache.org/SXuo
We should fix them as soon as possible to release
od
testament to that fact.)
On May 17, 2016, at 4:40 PM, Akira Ajisaka <aajis...@apache.org> wrote:
Is there some way for us to add a "Contributors2" group with the same
permissions as a workaround? Or we could try to clean out contributors
who are no longer active, but tha
umar B <
> vinayakumarb.apa...@gmail.com
<mailto:vinayakumarb.apa...@gmail.com>> wrote:
>
> > Thanks Akira.
> > On 17 May 2016 10:59, "Akira Ajisaka" <aajis...@apache.org
<mailto:aajis...@apache.org>> wrote:
> >
Hi Lei,
We don't need to do the followings:
> ssh people.apache.org
> cd /www/hadoop.apache.org/common
> svn up
The official document will be updated automatically. Now your name is in
the PMC list. http://hadoop.apache.org/who.html
I'll update the wiki to reflect that.
Thanks,
Akira
On
+1.
- Checked out HADOOP-12930
- Built by "mvn package -Pdist -DskipTests -Dtar" successfully
- Added custom subcommands to ~/.hadooprc and confirmed they worked
- Built documentation and it looks good
Thanks,
Akira
On 5/15/16 02:33, Allen Wittenauer wrote:
This vote closes in 2 days and the
Hi Vinay,
Added you into committer roles for HADOOP/MAPREDUCE/YARN.
Regards,
Akira
On 5/17/16 13:45, Vinayakumar B wrote:
Hi Junping,
It looks like, I too dont have permissions in projects except HDFS.
Please grant me also to the group.
Thanks in advance,
-Vinay
On 17 May 2016 6:10 a.m.,
Reverted e20542 from branch-2 and commented that in HADOOP-13157.
Thanks Xiao for reporting this and thanks Sangjin for investigating the
issue.
Regards,
Akira
On 5/18/16 10:28, Sangjin Lee wrote:
No, I think it is this commit:
Added Arun Suresh into committer role in MAPREDUCE.
Added Yufei Gu into contributor role in HDFS.
Thanks,
Akira
On 5/18/16 14:08, Yufei Gu wrote:
I guess I lost my contributor role in HDFS, since I cannot comment in HDFS.
Best,
Yufei
On Tue, May 17, 2016 at 9:48 PM, Akira AJISAKA
<aj
.
Could you restore the role?
Regards
Kai Sasaki
——
Kai Sasaki
lewua...@me.com
On May 18, 2016, at 14:13, Akira AJISAKA <ajisa...@oss.nttdata.co.jp> wrote:
Added Arun Suresh into committer role in MAPREDUCE.
Added Yufei Gu into contributor role in HDFS.
Thanks,
Akira
On 5/18/16 14:08, Yu
Hi developers,
Before cutting 3.0.0-alpha RC, I'd like to drop JDK7 support in trunk.
Given this is a critical change, I'm thinking we should get the
consensus first.
One concern I think is, when the minimum version is set to JDK8, we need
to configure Jenkins to disable multi JDK test only
+1 for marking HADOOP-9613 as incompatible change and upgrading the
version in trunk.
Thanks,
Akira
On 5/9/16 12:12, Tsuyoshi Ozawa wrote:
Hi developers,
We’ve worked on upgrading jersey(HADOOP-9613) for a years. It's
essential change to support complication with JDK8. It’s almost there.
Thanks Vinod and Andrew for the summary.
> Here's an attempt at encoding this policy as a set of rules for
setting fix
> versions (credit to Allen):
>
> 1) Set the fix version for all a.b.c versions, where c > 0.
> 2) For each major release line, set the lowest a.b.0 version.
Assuming
+1 for the source tarball.
- Downloaded source tarball and binary tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Compiled Hive 2.1.0/1.2.1 and Tez 0.8.4/0.7.1 using Hadoop 2.7.3 pom
successfully
- Ran some Hive on Tez queries successfully
Thanks,
Hi folks,
qbt for trunk+JDK8 on Linux/x86 is failing by
executable '/home/jenkins/tools/maven/latest3//bin/mvn' for 'maven' does
not exist.
Would someone fix this?
Regards,
Akira
On 7/21/16 00:41, Apache Jenkins Server wrote:
For more details, see
more valuable. e.g., pointing out that the leveldb changes in YARN have pretty
much completely broken it out of the box on non-x86.
On Jul 21, 2016, at 1:01 PM, Akira Ajisaka <ajisa...@oss.nttdata.co.jp> wrote:
Hi folks,
qbt for trunk+JDK8 on Linux/x86 is failing by
executable '/home/j
Hi Sangjin,
I'm thinking it's time for 2.6.5 release. Now there are 51 fixed issues
in 2.6.5 and the number is more than 2.6.4 (47).
> How long do we maintain this line? What would be a sensible EOL policy?
Ideally 5 years, because most of our customers in Japan are using Hadoop
cluster
Today I hit the same issue.
Changing the browser to Firefox worked well for me.
-Akira
On 7/19/16 18:10, Zheng, Kai wrote:
Thanks Andrew for the work around!! It works great ...
Regards,
Kai
-Original Message-
From: Andrew Wang [mailto:andrew.w...@cloudera.com]
Sent: Wednesday, July
As I commented in the jira, I'm +1 for upgrading.
-Akira
On 6/29/16 10:16, Tsuyoshi Ozawa wrote:
No objections here?
- Tsuyoshi
On Mon, Jun 27, 2016 at 6:01 AM, Tsuyoshi Ozawa wrote:
Hi developers,
I will plan to upgrade Google Guice dependency on trunk. The change
also
the project has in its history. If the list
is too long, maybe we can put them in another list, like OLD_CONTRIBUTORS.
Regards,
Kai
-Original Message-
From: Akira AJISAKA [mailto:ajisa...@oss.nttdata.co.jp]
Sent: Saturday, June 18, 2016 12:56 PM
To: Zheng, Kai <kai.zh...@intel.com>; comm
Hi Marton,
This is intentional. source htmls were removed.
https://issues.apache.org/jira/browse/HADOOP-13688
Regards,
Akira
On 2017/01/22 0:50, Marton Elek wrote:
hadoop-3.0.0-alpha2.tar.gz is much more smaller than
hadoop-3.0.0-alpha1.tar.gz. (246M vs 316M)
The big difference is the
Thanks Vinod for cutting another RC.
+1
- Downloaded source tarball and binary tarball
- Verified signatures and checksums
- Compiled and built a single node cluster
- Compiled Hive 2.1.0/1.2.1 and Tez 0.8.4/0.7.1 using Hadoop 2.7.3 pom
successfully
- Ran some Hive on Tez queries successfully
-1 (binding)
HADOOP-13434 and HADOOP-11814, committed between RC0 and RC1, are not
reflected in the release note.
-Akira
On 8/17/16 13:29, Allen Wittenauer wrote:
-1
HDFS-9395 is an incompatible change:
a) Why is not marked as such in the changes file?
b) Why is an incompatible change
Thanks Andrew for the great work.
+1 (binding)
- Downloaded source and verified checksum and signature
- Compiled with -Pnative @ CentOS 7.2 and OpenJDK 8u101
- Ran some MapReduce jobs successfully
- Checked Web UIs and logs
- hdfs/yarn/mapred "--daemon" option works as expected
Regards,
Akira
eople to. Same permissions as "Contributors." This applies to all
of the projects using Hadoop Permissions (includes common and HDFS.)
-Akira
On 8/24/16 14:16, Akira Ajisaka wrote:
How about we try to do some grouping, where we just have sub groups,
hadoop-contributors-1, hadoop-contribut
Yes. I can help with releasing them.
-Akira
On 9/9/16 15:31, Tsuyoshi Ozawa wrote:
Chiwan Park reported Hadoop incompatibility by the change of HADOOP-11252.
Now, HADOOP-13579 is committed to branch-2.6 and branch-2.7.
complement: HADOOP-13579 fixes the problem of incompatibility by
> How about we try to do some grouping, where we just have sub groups,
> hadoop-contributors-1, hadoop-contributors-2, ... and add them as
> contributors; we then edit group membership, adding a new group when the
> current one gets above some chosen size limit?
Agreed. Filed INFRA-12487.
-0 (binding)
- Downloaded source tarball and binary tarball
- Verified signatures and checksums
- Compiled successfully with both JDK6 and JDK7
- Compiled and built a single node cluster
- Compiled Hive 1.2.1 and Tez 0.7.1/0.8.4 using Hadoop 2.6.5 pom
successfully
- Ran some Hive on Tez/MRv2
I'm +1 for using Git "Signed-off-by" feature.
Regards,
Akira
On 11/5/16 17:36, Brahma Reddy Battula wrote:
Hi All,
When we look at current git log,commit message patters are like following..
I feel, we should have unified one. Might not be very important,but it will be
better have unified
In more detail, I'm +1 for requiring 'git format-patch' and commit with
'dev-support/bin/smart-apply-patch --committer', as well as Apache Yetus.
That way committers can use signed-off feature and don't need to add
'contributed by ...' to commit message by hand.
Thanks,
Akira
On 11/8/16
It's almost a year since branch-2.8 has cut.
I'm thinking we need to release 2.8.0 ASAP.
According to the following list, there are 5 blocker and 6 critical issues.
https://issues.apache.org/jira/issues/?filter=12334985
Regards,
Akira
On 10/18/16 10:47, Brahma Reddy Battula wrote:
Hi Vinod,
1 - 100 of 880 matches
Mail list logo