Ashish, In one perspective all of perl and CPAN is a very powerful ETL package. I would argue that it's ability to stitch practically any system to another system while mangling the data in transit to your your own specification is not exceeded anywhere. There are languages and tools outside perl where the process is more standardized for specific industry flows. However, with that standardization comes some inflexibility. Many if not most of the pieces of those tools also exist in the CPAN-verse in a pretty standardized format also. They just aren't collated together under an ETL or data warehouse header. You will be most successful in building ETL flows for your needs with perl by searching for each piece of your ETL flow separately rather than looking for a one stop shop. For instance Nelson built his data stuff on DBI <https://metacpan.org/pod/DBI> and DBIx <https://metacpan.org/search?q=DBIx&size=20>. While Nelsons packages aren't doing so well in the CPAN testers universe you may find that DBI and DBIx already provide sufficient functionality for your needs without his wrapper. Both of those packages are battle tested in many ways and link quite well to all of the other interesting things on CPAN.
I myself have never had to go outside perl to execute ETL. Best Regards, Jed On Tue, May 19, 2015 at 8:57 AM, Ashish Mukherjee < ashish.mukher...@gmail.com> wrote: > Hello, > > I have been searching for some perl modules related to DataWarehouse needs > and came across few elementary DataWarehouse modules on CPAN by Nelson > Ferraz, which have been last updated in 2010. I tried reaching out to him > over the list previously, without success. > > I was wondering the following - > > 1. Do others also have similar requirements in perl? i.e modules for ETL, > DataWarehousing etc. > > 2. Do people on this list have certain other requirements which are not so > apparent too, but perhaps being met by frameworks in other languages? > > If I am unable to reach Nelson, I was thinking of following the process to > take custodianship of the modules and work on them further. > > Regards, > Ashish >
