Distcp (I have a use case for it) Hadoop-federation-balance(RBF uses it, we will take care in case it bothers) Hadoop-Dynamometer(This I feel is being used from jira activies)
So, these three we should let stay as is. Others the object store ones are active. You know which all are needed. For rest we can call for a vote and drop them if everyone agrees. -Ayush > On 31-Mar-2022, at 4:40 PM, Steve Loughran <ste...@cloudera.com.invalid> > wrote: > > how many of the modules under hadoop-tools get used/maintained? > > hadoop-aliyun > hadoop-ant > hadoop-archive-logs > hadoop-archives > hadoop-aws > hadoop-azure > hadoop-azure-datalake > hadoop-datajoin > hadoop-distcp > hadoop-dynamometer > hadoop-extras > hadoop-federation-balance > hadoop-fs2img > hadoop-ftp > hadoop-gridmix > hadoop-kafka > hadoop-openstack > hadoop-ozone > hadoop-pipes > hadoop-resourceestimator > hadoop-rumen > hadoop-sls > hadoop-streaming > > I know distcp is universal, and the aws. azure, aliyun modules are > active. hadoop-azure-datalake doesn't get maintenance, but it should stay > around until microsoft remove the gen1 ADLS service > > But what about all the others? the hadoop-openstack one hasn't been touched > or tested for a few years, and IMO could be cut immediately. what about > others? does hadoop-streaming or hadoop-pipes get use any more? > > Existing code may use these, but having them in the codebase only creates > maintenance work, especially if security fixes need to go in on the code or > are caused by dependencies. --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
