Review Request for HADOOP-8476 and HADOOP-8160

Hi, Please some one review patches for https://issues.apache.org/jira/browse/HADOOP-8476 https://issues.apache.org/jira/browse/HADOOP-8160 Thanks in advance. Regards, Vinay

RE: Need help for building haddop source on windows 7

Hi.. As Kai told you can build trunk or branch 2.1 in windows with native support. Please check Readme You may need to install 1. Windows 7 SDK 2. .NET framework 4 Regards, Vinayakumar B On Sep 5, 2013 3:45 PM, Zheng, Kai kai.zh...@intel.com wrote: Just updated by Harsh J. Thanks. The trunk

Re: [VOTE] Release Apache Hadoop 2.1.1-beta

Thanks arun for the rc. But I would like HDFS-5031 to be in. Please someone have a look. Correct me if this issue not harming the release. Regards, Vinayakumar B On Sep 18, 2013 10:29 AM, Roman Shaposhnik r...@apache.org wrote: On Mon, Sep 16, 2013 at 11:38 PM, Arun C Murthy

[Important] Checksum Error while appending to the file.

block size in Step 4 and Step 5 are matching, but metafile sizes are not matching. Thanks and Regards, Vinayakumar B

RE: [DISCUSS] Clarification on Compatibility Policy: Upgraded Client + Old Server

to explicitly mention about the compatibility of existing APIs in both versions. Anyway this is not applicable for the new APIs in latest client and this is understood. We can make it explicit in the document though. Regards, Vinayakumar B -Original Message- From: Chris Nauroth [mailto:cnaur

Re: Plans of moving towards JDK7 in trunk

+1 for keeping jdk 6 suppprt in branch-2 and start using jdk 7 in trunk. I agree that this approach makes patch generation difficult for branch-2 and trunk. Also the actual benefit and real issues after start using jdk7 will be known only if atleast one of the release is out in trunk version.

[Important] Confirmation related to OpenSsl security issue

Hi, Recently one security issue has been found in OpenSSL which has impacted so many customers of different vendors. http://www.kb.cert.org/vuls/byvendor?searchviewQuery=FIELD+Reference=720951SearchOrder=4 I want to ask, whether is there in impact of this on the Hadoop Release? Currently

Re: HADOOP_ROOT_LOGGER

Hi Robert, I understand your confusion. HADOOP_ROOT_LOGGER is set to default value INFO,console if it hasn't set for anything and logs will be displayed on the console itself. This will be true for any client commands you run. For ex: hdfs dfs -ls / But for the server scripts (hadoop-daemon.sh,

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

+1 (binding) Regards, Vinay On Wed, Jun 25, 2014 at 4:13 AM, Vinod Kumar Vavilapalli vino...@apache.org wrote: +1 Vinod On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release

Why Hadoop-trunk-commit always fails?

Hi, Hadoop-trunk-commit build always fails with message similar to below. Anybody knows about this? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (depcheck) on project hadoop-yarn-server-tests: Some Enforcer rules have failed. Look above for specific

Re: [DISCUSS] Assume Private-Unstable for classes that are not annotated

I think, in API docs contains only classes which are marked as @Public. no? Regards, Vinay On Wed, Jul 23, 2014 at 5:24 AM, Andrew Wang andrew.w...@cloudera.com wrote: +1 On Tue, Jul 22, 2014 at 3:44 PM, Sandy Ryza sandy.r...@cloudera.com wrote: That policy makes sense to me. We

Re: Git repo ready to use

Hi Karthik, Good to see migration completed. Currently, *branch-2.5* points to *trunk *itself. I think it should point to *origin/branch-2.5 *right? Regards, Vinay On Wed, Aug 27, 2014 at 2:10 PM, Karthik Kambatla ka...@cloudera.com wrote: Oh.. a couple more things. The git commit hashes

Re: Git repo ready to use

at 2:19 AM, Vinayakumar B vinayakum...@apache.org wrote: Hi Karthik, Good to see migration completed. Currently, *branch-2.5* points to *trunk *itself. I think it should point to *origin/branch-2.5 *right? Are you referring to your local branch-2.5? What is origin? branch-2.5

Re: Git repo ready to use

I think its still pointing to old svn repository which is just read only now. You can use latest mirror: https://github.com/apache/hadoop Regards, Vinay On Sep 4, 2014 11:37 AM, Sangjin Lee sjl...@gmail.com wrote: It seems like the github mirror at https://github.com/apache/hadoop-common has

Re: Redirect Writes/Reads to a particular Node

Hi Dhiraj, Unfortunately there is no such feature available in HDFS. HDFS is designed to utilize all the datanodes available in the cluster and serve maximum clients by distributing the load to different datanodes. Anyway, there is one workaround for this. You can place your client (both

Re: Guava

As Haohui Mai said, removing the dependency on the Guava may not be a good idea. But, instead can we use a fixed guava version in Hadoop which is stable as of now, with a shaded package structure ? so that it will not break the application level dependency on another version of the Guava. Inside

Re: submitting a hadoop patch doesn't trigger jenkins test run

As I mentioned jn HADOOP-11293, This is not issue of any script, but the execution time. Actually jenkins is getting triggered. But since changes involves multiple projects, executing tests for all those projects taking more time. currently in jenkins if build time is more than 5 hours, then

Re: First Patch HADOOP-10483

Hi Alec, Glad that you are interested in contributing to Hadoop. Generally for merging patches for trivial issues varies. If any committer reviews and gives +1 and if there are no more objections from anyone, immediately it can be merged, Soon I will take a look at the patch you posted in

Re: Consolidation of common jars across projects

I have attempted this sometime back. HADOOP-10115 https://issues.apache.org/jira/browse/HADOOP-10115. changed only the packaging part though. Its little old patch. Not sure whether it applies properly on latest trunk. Anyway I will also re-check it. Regards, Vinay On Wed, Dec 17, 2014 at 9:59

Re: [Hadoop] AvroRecord cannot be resolved

Hi, I believe you have generated the eclipse project files using the eclipse:eclipse goal. This generates the project files for hadoop-common project without the genarated test sources added as source folder. I really dont know why this happens. But, You can resolve it by Just adding,

Re: Jira down :(

at 3:08 PM, Vinayakumar B vinayakum...@apache.org wrote: I am getting 502 error from Jira. Does anybody know whom to contact to resolve it? Regards, Vinay

Jira down :(

I am getting 502 error from Jira. Does anybody know whom to contact to resolve it? Regards, Vinay

Re: [DISCUSS] More Maintenance Releases

+1 for the idea of maintenance releases. Considering the amount code changes done in trunk and branch-2, cherry-picking may not be easy and straight forward in all issues. I would love to help in cherry-picking the fixes and reviewing them. I would also love to help in release process.

Re: [DISCUSS] git rebase vs. git merge for branch development

+1, I agree with the support for git-merge based workflows for large branch merge. I have experienced the pain of re-basing the entire branch HDFS-7285, just for verification though, and I found even a line change in trunk in core files ( ex: FSNameSystem.java, BlockManager.java ) makes it hard

Re: [VOTE] Using rebase and merge for feature branch development

+1, -Vinay On Aug 24, 2015 11:29 PM, Colin P. McCabe cmcc...@apache.org wrote: +1 cheers, Colin On Mon, Aug 24, 2015 at 10:04 AM, Steve Loughran ste...@hortonworks.com wrote: +1 (binding) On 21 Aug 2015, at 13:44, Andrew Wang andrew.w...@cloudera.com wrote: Hi common-dev, As

Re: Planning Hadoop 2.6.1 release

offline) and any outside cherry-picks are going to disrupt our progress. If you want something added to 2.6.1, please post it in the mailing lists and we will consider it. Thanks. +Vinod On Aug 14, 2015, at 12:17 AM, Vinayakumar B vinayakum...@apache.org wrote: FYI, Some

Re: Hadoop 2.6.1 Release process thread

1. HDFS-7446 https://issues.apache.org/jira/browse/HDFS-7446 : HDFS inotify should have the ability to determine what txid it has read up to This is also marked for 2.6.1, but this changes the client protocol and protobuf messages. Please confirm whether this is Compatible change with

Re: [DISCUSS] Additional maintenance releases for Hadoop 2.y versions

+1 for steve's suggestion. I agree completely that everything should be finalized before committing in. -Vinay On Jul 16, 2015 2:29 PM, Steve Loughran ste...@hortonworks.com wrote: 1. I agree that the bar for patches going in should be very high: there's always the risk of some subtle

Re: [VOTE] Release Apache Hadoop 2.6.2

+1 binding, 1. Built the tar from the git tag checkout 2. Verified the release notes both downloaded and built 3. Installed single node cluster and ran some jobs successfully 4. Verified documents, Found "svn" link instead of git in the header of document. This could be corrected either in next

Re: FYI: Major, long-standing Issue with trunk's test-patch

So I’m going to turn on Yetus for *ALL* Hadoop precommit jobs > later tonight. (Given how backed up Jenkins is at the moment, there is > plenty of time. haha) Anyway, if you see “Powered by Yetus” in the Hadoop > QA posts, you’ve got Yetus. If you don’t see it, it ran on trunk’s > test-patch.

Re: FYI: Major, long-standing Issue with trunk's test-patch

, 2015 at 9:48 AM, Sean Busbey <bus...@cloudera.com> wrote: > On Wed, Oct 28, 2015 at 9:23 PM, Vinayakumar B <vinayakum...@apache.org> > wrote: > > So I’m going to turn on Yetus for *ALL* Hadoop precommit jobs > >> later tonight. (Given how backed up Jenkins is at

RE: [VOTE] Release Apache Hadoop 2.7.2 RC0

I think one recent critical issue HDFS-9413, getContentSummary() on standby should throw StandbyException, Found by Brahma, is a good candidate for 2.7.2 as well. -vinay On Nov 14, 2015 5:20 AM, "Naganarasimha G R (Naga)" < garlanaganarasi...@huawei.com> wrote: > Hi Vinod, > > Can you also look

Re: [YETUS] Yetus TLP approved

That's excellent news. Congrats guys. -Vinay On Sep 17, 2015 10:15 PM, "Tsuyoshi Ozawa" wrote: > Congrats, and thanks for your awesome effort, Sean. > > - Tsuyoshi > > On Fri, Sep 18, 2015 at 1:14 AM, Chris Nauroth > wrote: > > That's great news.

Re: Local repo sharing for maven builds

temporary workaround, could we reduce the # > of execs per node to 1? Our build queues are pretty short right now, so I > don't think it would be too bad. > > Best, > Andrew > > On Wed, Sep 23, 2015 at 12:18 PM, Vinayakumar B <vinayakum...@apache.org> > wrote: > &g

Re: Local repo sharing for maven builds

which > can be pretty expensive. A du -h ~/.m2 tells me I have an 11GB local cache. > > > > On 26 Sep 2015, at 06:43, Vinayakumar B <vinayakum...@apache.org> wrote: > > > > Thanks Andrew, > > > > May be we can try making it to 1 exec, and try for s

Re: Planning for Apache Hadoop 2.6.2

15 at 9:39 PM, Akira AJISAKA < > >> ajisa...@oss.nttdata.co.jp> wrote: > >> > >>> 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 wit

Re: Local repo sharing for maven builds

In case if we are going to have separate repo for each executor, I have checked, each jenkins node is allocated 2 executors. so we only need to create one more replica. Regards, Vinay On Wed, Sep 23, 2015 at 7:33 PM, Steve Loughran wrote: > > > On 22 Sep 2015, at

Re: Local repo sharing for maven builds

On Tue, Sep 22, 2015 at 9:09 PM, Colin P. McCabe wrote: > On Mon, Sep 21, 2015 at 4:08 AM, Steve Loughran > wrote: > > > >> On 19 Sep 2015, at 04:42, Allen Wittenauer wrote: > >> > >> a) Multi-module patches are always troublesome

Re: Planning for Apache Hadoop 2.6.2

Thanks Vinod and Sangjin for making 2.6.1 release possible. Apologies for not getting time to verify and vote for the release. I will also be available to help for 2.6.2 if anything required. Thanks, Vinay On Fri, Sep 25, 2015 at 12:16 AM, Vinod Vavilapalli wrote: >

Re: Disable some of the Hudson integration comments on JIRA

Yes, thats good idea. -Vinay On Thu, Nov 26, 2015 at 10:29 AM, Zhe Zhang wrote: > I think that's a good idea. Thanks for the proposal Andrew. > > --- > Zhe Zhang > > On Wed, Nov 25, 2015 at 5:41 PM, Andrew Wang > wrote: > > > Hi all, > > > >

[Important] What is the practical maximum HDFS blocksize used in clusters?

Hi All, Just wanted to know, what is the maximum and practical dfs.block.size used in production/test clusters. Current default value is 128MB and it can support upto 128TB ( Yup, right. It's just a configuration value though) I have seen clusters using upto 1G block size for big files.

Re: Github integration for Hadoop

INFRA-11597 has been fixed. Now all github mails are diverted to common-iss...@hadoop.apache.org -Vinay On Tue, Apr 5, 2016 at 1:05 PM, Vinayakumar B <vinayakumar...@huawei.com> wrote: > https://issues.apache.org/jira/browse/INFRA-11597 has been filed for this. > > -Vinay &g

Re: Github integration for Hadoop

bq. We don't spam common-dev about every time a new patch attachment gets posted to an existing JIRA. We shouldn't do that for github either. Is there any update on this. ? Any INFRA ticket filed to disable these mails? Because, I am sure, people would have got frustrated by seeing mails

RE: Github integration for Hadoop

these mails. C. On Mon, Apr 4, 2016, at 06:21, Vinayakumar B wrote: > bq. We don't spam common-dev about every time a new patch attachment > gets posted to an existing JIRA. We shouldn't do that for github > either. > > Is there any update on this. ? > Any INFRA ticket filed to d

Re: Different JIRA permissions for HADOOP and HDFS

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., "Sangjin Lee" wrote: Thanks Junping! It seems to work now. On Mon, May 16, 2016 at 5:22 PM, Junping Du

Re: Different JIRA permissions for HADOOP and HDFS

Thanks Akira. On 17 May 2016 10:59, "Akira Ajisaka" <aajis...@apache.org> wrote: > Hi Vinay, > > Added you into committer roles for HADOOP/MAPREDUCE/YARN. > > Regards, > Akira > > On 5/17/16 13:45, Vinayakumar B wrote: > >> Hi Junping, >> &g

RE: [VOTE] Release Apache Hadoop 2.7.3 RC0

+1 (binding) 1. Downloaded and Built from branch-2.7.3 2. Started up HDFS and YARN in Single Node cluster. 3. Ran WordCount job multiple times and Success. 4. Verified the "Release Notes" available at the URL mentioned by Vinod. Apart from that, Faced same issues as Andrew wang, while running

Hadoop 2.8.1 docs not available at http://hadoop.apache.org/docs/r2.8.1/

There are no webpages available in the below docs directory. All it lists is empty directories. http://hadoop.apache.org/docs/r2.8.1/ -Vinay

Re: [VOTE] Release Apache Hadoop 3.0.1 (RC0)

+1 Binding, 1. Checked out code from tag. 2. Built and deployed a 3-node docker cluster in secure mode (HDFS HA, Non-HA YARN). Docker script available in [1], if anyone need, 3. Ran wordcount job successfully. 4. Verified basic webhdfs commands using curl. 5. Verified basic HDFS commands [1]

Re: Can't pull the trunk code in windows- >File name too long

this is happening in Windows, Please somebody from yarn look into this. -Vinay On 13 Mar 2018 11:30 am, "Brahma Reddy Battula" < brahmareddy.batt...@huawei.com> wrote: Hi Not able to pull/clone the trunk code. Does it possible make following shorten. fatal: cannot create directory at

Re: HADOOP-14163 proposal for new hadoop.apache.org

+1, New site looks great. Just one nit in README '--refresh' flag for hugo server no longer available. -Vinay On Mon, 3 Sep 2018, 10:21 am Shashikant Banerjee, wrote: > +1 > > Thanks > Shashi > > On 9/3/18, 9:23 AM, "Mukul Kumar Singh" wrote: > > +1, Thanks for working on this Marton. >

Re: [DISCUSS] Move to gitbox

+1 -Vinay On Mon, 10 Dec 2018, 1:22 pm Elek, Marton > Thanks Akira, > > +1 (non-binding) > > I think it's better to do it now at a planned date. > > If I understood well the only bigger task here is to update all the > jenkins jobs. (I am happy to help/contribute what I can do) > > > Marton > >

Including Original Author in git commits.

Hi all, Right now we are committing with commitrer name as author and adding contributor name in commit message. This way of committing will not reflect in contributors git profile. I believe current way of crediting.. is based on SVN days.. Since now all apache repos are following git.. we can

Re: Including Original Author in git commits.

So.. if we started doing that already.. we can encourage contributors to attach formatted patch.. or create PRs. And update wiki to follow exact steps to contribute and commit. -Vinay On Thu, 14 Feb 2019, 4:54 pm Steve Loughran I've been trying to do that recently, though as it forces me to

Re: [VOTE] Release Apache Hadoop 3.1.2 - RC1

Sorry for being late. Thanks everyone for the Release efforts. +1 (Binding) -Built from tag on Ubuntu-18.04 -Successful Native build. -Deployed a 3-Node docker cluster with kerberos Security Enabled on Centos7 images. -Verified basic HDFS Commands -Ran basic wordcount Job. -Vinay On Wed, Feb

Re: [VOTE]: Support for RBF data locality Solution

+1 for approach A. On Thu, 11 Apr 2019, 12:23 pm Akira Ajisaka, wrote: > The Approach A looks good to me. > > Thanks, > Akira > > On Thu, Apr 11, 2019 at 2:30 PM Xiaoqiao He wrote: > > > > Hi forks, > > > > The current implementation of RBF is not sensitive about data locality, > > since

[ANNOUNCE] New Apache Hadoop Committer - Ayush Saxena

Congratulations & Welcome aboard Ayush! Vinayakumar B (On behalf of the Hadoop PMC)

[ANNOUNCE] New Apache Hadoop Committer - Ayush Saxena

Congratulations & Welcome aboard Ayush! Vinayakumar B (On behalf of the Hadoop PMC)

[DISCUSS] ARM/aarch64 support for Hadoop

Hi Folks, ARM is becoming famous lately in its processing capability and has got the potential to run Bigdata workloads. Many users have been moving to ARM machines due to its low cost. In the past there were attempts to compile Hadoop on ARM (Rasberry PI) for experimental purposes. Today ARM

Re: [VOTE] Moving Submarine to a separate Apache project proposal

+1 Thanks for the proposal. Its very interesting project and looks very promising one by looking at the participations from various companies and the speed of development. I would also like to participate in the project. Please add me as well. Thanks, -Vinay On Tue, 3 Sep 2019, 12:38 pm Rakesh

Re: [DISCUSS] ARM/aarch64 support for Hadoop

t even without ARM, this is a > great idea. > > If you like we can get together during one of the HDFS meetups hosted by > Wei-chiu. > > Thanks > Anu > > > > On Thu, Sep 5, 2019 at 3:19 AM Vinayakumar B > wrote: > >> Hi all, >> >> Thanks fo

Re: [DISCUSS] ARM/aarch64 support for Hadoop

t;> separate >> >> >>> branch with it's own ARM CI seems a really good idea. >> >> >>> By doing this we won't break any of the undergoing development in >> >> trunk >> >> >> and >> >> >>> a CI can be a very

Re: [NOTICE] Building trunk needs protoc 3.7.1

Hi Vinay, > > > > A bit confused, I saw the HADOOP-13363 is still pending. Do we need to > > upgrade protobuf version to 3.7.1 NOW or once HADOOP-13363 is completed? > > > > Thanks, > > Wangda > > > > On Fri, Sep 20, 2019 at 8:11 AM Vinayakumar B >

Re: Daily Builds Getting Aborted Due To Timeout

Thanks Ayush, I think possible other ways are improving the test runtime. 1. try "parallel-tests" profile if applicable on all modules whichever is okay with tests running in parallel. This may reduce the total unit tests runtime drastically. ex: I can see hadoop-hdfs-rbf takes around ~22 min.

[DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

ed with the proposal. -Thanks, Vinay On Fri, Sep 27, 2019 at 11:54 AM Vinod Kumar Vavilapalli wrote: > Moving the thread to the dev lists. > > Thanks > +Vinod > > > On Sep 23, 2019, at 11:43 PM, Vinayakumar B > wrote: > > > > Thanks Marto

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

llowed in HBase. May be people involved in HBase can add some points here. Thoughts? > > .. Owen > > On Fri, Sep 27, 2019 at 8:38 AM Vinayakumar B > wrote: > >> Hi All, >> >>I wanted to discuss about the separate repo for thirdparty dependencies >> which

Re: [NOTICE] Building trunk needs protoc 3.7.1

this only when there are changes related to shaded dependencies. -Vinay On Sun, 22 Sep 2019, 10:11 pm Steve Loughran, wrote: > > > On Sun, Sep 22, 2019 at 3:22 PM Vinayakumar B > wrote: > >>Protobuf provides Wire compatibility between releases.. but not >

Re: [NOTICE] Building trunk needs protoc 3.7.1

> On Sep 21, 2019, at 9:55 AM, Vinayakumar B > wrote: > > > > @Wangda Tan , > > Sorry for the confusion. HADOOP-13363 is umbrella jira to track multiple > > stages of protobuf upgrade in subtasks. (jar upgrade, Docker update, > plugin > > upgrade, sha

Re: Some updates for Hadoop on ARM and next steps

Hi all, As a starter.. Created a simple mvn based job (not yetus and docker as current qbt on trunk on x86) in https://builds.apache.org/job/Hadoop-qbt-linux-ARM-trunk/7/console Right now using the manual tools installed and the previous workarounds mentioned related to various third-party

Re: Some updates for Hadoop on ARM and next steps

Also note that.. Nothing gets deployed back to maven central repo from this job. So no interference with other jobs and nodes as well. -Vinay On Thu, 28 Nov 2019, 10:55 pm Vinayakumar B, wrote: > Hi all, > > As a starter.. > Created a simple mvn based job (not yetus and docker as

[NOTICE] Building trunk needs protoc 3.7.1

Hi All, A very long pending task, protobuf upgrade is happening in HADOOP-13363. As part of that protobuf version is upgraded to 3.7.1. Please update your build environments to have 3.7.1 protobuf version. BUILIDING.txt has been updated with latest instructions. This pre-requisite to update

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

> > > https://lists.apache.org/thread.html/f12c589baabbc79c7fb2843422d4590bea982cd102e2bd9d21e9884b@%3Cdev.hbase.apache.org%3E > > > Thanks. > > Vinayakumar B 于2019年9月28日周六 上午1:28写道： > > > Please find replies inline. > > > > -Vinay > > > > On Fri

[VOTE] Release Apache Hadoop Thirdparty 1.0.0

Hi folks, Thanks to everyone's help on this release. I have created a release candidate (RC0) for Apache Hadoop Thirdparty 1.0.0. RC Release artifacts are available at : http://home.apache.org/~vinayakumarb/release/hadoop-thirdparty-1.0.0-RC0/ Maven artifacts are available in staging repo:

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

https://issues.apache.org/jira/browse/HADOOP-16895 jira created for handling LICENCE and NOTICEs PR also has been raised for a proposal. Please validate https://github.com/apache/hadoop-thirdparty/pull/6 -Vinay On Fri, Feb 28, 2020 at 11:48 PM Vinayakumar B wrote: > Thanks Elek for detai

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

> > ps: I am not experienced with licensing enough to judge which one of > these are blocking and I might be wrong. > > IMO, none of these should be blocking and can be handled before next release. Still if someone feels this should be fixed and RC should be cut again, I am open to it.

[DISCUSS] hadoop-thirdparty 1.0.0 release

Hi All, Since Hadoop-3.3.0 release is around the corner, its time to release hadoop-thirdparty's first ever release, without which hadoop-3.3.0 cannot proceed for release. Below are the tentative date for RC and release. Since there is no much activity in this repo (other than the opentracing

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

unification we can think > > parallel thread as Vinay mentioned). > > > > > > > > On Mon, 6 Jan 2020 at 6:21 PM, Vinayakumar B > > wrote: > > > >> Hi Sree, > >> > >>> apache/hadoop-thirdparty, How would it fit into ASF ? As an Incubating >

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

? Looking at HBase > as an example, it looks like everything that are known to break a lot after > an update get shaded into the hbase-thirdparty artifact: guava, netty, ... > etc. > Is it the purpose to isolate these naughty dependencies? > > On Wed, Oct 9, 2019 at 12:38 PM Vinayakumar B

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

st course of action.I am looking at, no projects > > should ever had to shade any artifacts except as an absolute necessary > > alternative. > > > > > > Thank you./Sree > > > > > > > > On Saturday, January 4, 2020, 7:49:18 AM PST, Vinayakumar B < > > v

[NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

Hi All, This mail is to notify about the Removal of following public APIs from Hadoop Common. ClassName: org.apache.hadoop.security.token.Token APIs: public Token(TokenProto tokenPB); public TokenProto toTokenProto(); Reason: These APIs are having Generated

[VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

Hi folks, Thanks to everyone's help on this release. I have re-created a release candidate (RC1) for Apache Hadoop Thirdparty 1.0.0. RC Release artifacts are available at : http://home.apache.org/~vinayakumarb/release/hadoop-thirdparty-1.0.0-RC1/ Maven artifacts are available in staging

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

checksums and tried building from source. > Everything seems to be working fine. > But I feel the concerns regarding licences are valid. > IMO we should fix them and include HADOOP-16895 too in the release > > -Ayush > > > On 29-Feb-2020, at 1:45 AM, Vinayakumar B > wrote

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

ier. > > Other downstreamers that break with the relocated protobuf include: Ozone > and HBase. but neither of them use the removed Token API. > > > On Wed, Jan 8, 2020 at 4:40 AM Vinayakumar B > wrote: > >> Hi All, >> >>This mail

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

rotocolPB/StorageContainerLocationProtocolClientSideTranslatorPB.java:[116,47] > > incompatible types: com.google.protobuf.ServiceException cannot be > > converted to org.apache.hadoop.thirdparty.protobuf.ServiceException > > 17:01:19 2020/04/16 00:01:19 INFO: [INFO] 2 errors > > > > > > There's anoth

Re: [DISCUSS] making Ozone a separate Apache project

+1 -Vinay On Thu, 14 May 2020, 12:20 pm Surendra Singh Lilhore, < surendralilh...@gmail.com> wrote: > +1 > > -Surendra > > > On Thu, 14 May, 2020, 9:30 am yisheng lien, wrote: > > > +1 > > > > Thank you Marton for the detailed description. > > > > > > Wanqiang Ji 於 2020年5月14日 週四 上午11:27 寫道： >

[RESULT] [VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

trunk with hadoop-thirdparty 1.0.0 >> - Checked rat files and documents >> - Checked LICENSE and NOTICE files >> >> Thanks, >> Akira >> >> On Thu, Mar 12, 2020 at 5:26 AM Vinayakumar B >> wrote: >> >> > Hi folks, >> &g

Re: [RESULT] [VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

Thanks brahma. So total 5 +1s (4 binding, 1 non-binding). Done with pushing bits. Should get mirrored in next 24 hours. -Vinay On Thu, Mar 19, 2020 at 12:55 AM Brahma Reddy Battula wrote: > > My late +1.. I missed this.. > > > On Thu, 19 Mar 2020 at 12:43 AM, Vinayak

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

Making ARM artifact optional, makes the release process simpler for RM and unblocks release process (if there is unavailability of ARM resources). Still there are possible options to collaborate with RM ( as brahma mentioned earlier) and provide ARM artifact may be before or after vote. If

Re: [VOTE] Moving Ozone to a separated Apache project

+1 -Vinay On Fri, 25 Sep 2020 at 6:22 PM, Lin, Yiqun wrote: > +1. > > > > Thanks, > > Yiqun > > > > On 2020/9/25, 2:08 PM, "Elek, Marton" wrote: > > > > External Email > > > > Hi all, > > > > Thank you for all the feedback and requests, > > > > As we discussed in the previous

Re: [VOTE] Release Apache Hadoop 2.10.1 (RC0)

Apologies for delayed voting. +1 (Binding) 1. Verified the signature. Signatures are good. 2. Verified the sha512 checksum (I tried to use the sha512sum tool to verify. But ".sha512" files doesn't have the expected format. I guess these files are regenerated using "gpg --print-md",

Re: Wire compatibility between Hadoop 3.x client and 2.x server

iled jira https://issues.apache.org/jira/browse/HDFS-15660 for details > > > 2020年10月28日 17:08，Vinayakumar B 写道： > > Hi Wu,Jianliang, > Have you created the Jira for the issue you mentioned due to > getContentSummary? > > I might have a fix for this. Of-course it needs t

Re: Wire compatibility between Hadoop 3.x client and 2.x server

Hi Wu,Jianliang, Have you created the Jira for the issue you mentioned due to getContentSummary? I might have a fix for this. Of-course it needs to be applied both client and server side. Let me know. -Vinay On Wed, Oct 14, 2020 at 12:26 PM Wu,Jianliang(vip.com) < jianliang...@vipshop.com>

Re: [VOTE] Release Apache Hadoop 3.3.0 - RC0

+1 (Binding) -Verified all checksums and Signatures. -Verified site, Release notes and Change logs + May be changelog and release notes could be grouped based on the project at second level for better look (this needs to be supported from yetus) -Tested in x86 local 3-node docker cluster. +

[ANNOUNCE] New Apache Hadoop PMC member : Ayush Saxena

Hi all, I am very glad to announce that Ayush Saxena was voted to join Apache Hadoop PMC. Congratulations Ayush! Well deserved and thank you for your dedication to the project. Please keep up the good work. Thanks, -Vinay

[ANNOUNCE] New Apache Hadoop PMC member : Ayush Saxena

Hi all, I am very glad to announce that Ayush Saxena was voted to join Apache Hadoop PMC. Congratulations Ayush! Well deserved and thank you for your dedication to the project. Please keep up the good work. Thanks, -Vinay

Re: [VOTE] Release Apache Hadoop 3.3.1 RC3

+1 (Binding) 1. Built from Tag. 2. Successful Native Build on Ubuntu 20.04 3. Verified Checksums 4. Deployed the docker cluster with 3 nodes 5. Ran sample MR Jobs -Vinay On Sat, Jun 12, 2021 at 6:40 PM Ayush Saxena wrote: > +1, > Built from Source. > Successful Native Build on Ubuntu 20.04 >

Re: [DISCUSS] Hadoop 3.3.1 release

Hi David, >> Still hoping for help here: >> https://issues.apache.org/jira/browse/HDFS-15790 I will raise a PR for the said solution soon (in a day or two). -Vinay On Thu, 11 Mar 2021 at 5:39 AM, David wrote: > Hello, > > Still hoping for help here: > >

Re: [DISCUSS] Race condition in ProtobufRpcEngine2

Call.toString() was used only while sending the response, in the response processor thread. At this point, header would be already read and processed. So no chance of race conditions. This race condition was not introduced by the HADOOP-17046 ,

Re: [DISCUSS] cull unused modules from under hadoop-tools

Can move unused ones to separate repo under hadoop, and introduce a separate independent release cycle in case required. Any thoughts on this? -Vinay On Fri, 1 Apr 2022 at 1:31 PM, Ayush Saxena wrote: > Distcp (I have a use case for it) > Hadoop-federation-balance(RBF uses it, we will take

[ANNOUNCE] New Hadoop PMC member - Mukund Thakur

and welcome, Mukund ! -Vinayakumar B -- -Vinay

  1   2   >