Thanks for your email. Moving to the attic just does not mean that the product will not be available to use. Mature projects move to the Attic, but can still be available to users who want to continue using it.
>From the Apache Attic[1] project, moving to Apache Attic is intended to * Be non-impacting to users * Provide restricted oversight for these codebases * Provide oversight for active user lists with no Project Management Committee (PMC) Venkat On Thu, May 6, 2021 at 8:30 PM Deepak Vohra <dvohr...@yahoo.com.invalid> wrote: > > Venkat, > No new features, bug fixes and activities doesn't imply the Apache Sqoop > project has lost value. It could be that the project has reached maturity but > still has use. > > What alternative project exists to bulk transfer data between relational > databases and Apache Hadoop HDFS? > Projects like Apache Flume are for streaming data. Or Apache Kafka for > messaging, and Apache Beam for data pipelines. > Thanks,Deepak On Thursday, May 6, 2021, 12:13:30 AM EDT, Venkat > <venkatran...@apache.org> wrote: > > Hello Apache Sqoop community, > As you may have noticed, the last Apache Sqoop release was more than 3 years > ago. No new PMC member or committer has been added to the project in the > last 30 months. > Since the last release, features, bug fixes and activities on the > project have steadily > diminished.. > > Given this I would like to poll the community for roadmap suggestions > and contributions towards them > > If there are not any suggestions, moving the project to the Apache > Attic[1].is the best > approach that the community can take. > > Looking forward to your suggestions. > > Thanks, > > Venkat > > [1] http://attic.apache.org/ > -- Regards Venkat
