We performed a comparison between CloverETL and Pentaho Data Integration and Analytics based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."No dependence on native language and ease of use."
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"The area where Lumada has helped us is in the commercial area. There are many extractions to compose reports about our sales team performance and production steps. Since we are using Lumada to gather data from each industry in each country. We can get data from Argentina, Chile, Brazil, and Colombia at the same time. We can then concentrate and consolidate it in only one place, like our data warehouse. This improves our production performance and need for information about the industry, production data, and commercial data."
"Its drag-and-drop interface lets me and my team implement all the solutions that we need in our company very quickly. It's a very good tool for that."
"It makes it pretty simple to do some fairly complicated things. Both I and some of our other BI developers have made stabs at using, for example, SQL Server Integration Services, and we found them a little bit frustrating compared to Data Integration. So, its ease of use is right up there."
"Provides a good open source option."
"This solution allows us to create pipelines using a minimal amount of custom coding."
"Pentaho Data Integration is quite simple to learn, and there is a lot of information available online."
"It has improved our data integration capabilities."
"Sometimes, it took a whole team about two weeks to get all the data to prepare and present it. After the optimization of the data, it took about one to two hours to do the whole process. Therefore, it has helped a lot when you talk about money, because it doesn't take a whole team to do it, just one person to do one project at a time and run it when you want to run it. So, it has helped a lot on that side."
"Needs: easier automated failure recovery; more, and more intuitive auto-generated/filled-in code for components; easier/more automated sync between CloverETL Designer and CloverETL Server."
"Its documentation could be improved."
"Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough."
"The testing and quality could really improve. Every time that there is a major release, we are very nervous about what is going to get broken. We have had a lot of experience with that, as even the latest one was broken. Some basic things get broken. That doesn't look good for Hitachi at all. If there is one place I would advise them to spend some money and do some effort, it is with the quality. It is not that hard to start putting in some unit tests so basic things don't get broken when they do a new release. That just looks horrible, especially for an organization like Hitachi."
"I would like to see improvement when it comes to integrating structured data with text data or anything that is unstructured. Sometimes we get all kinds of different files that we need to integrate into the warehouse."
"The reporting definitely needs improvement. There are a lot of general, basic features that it doesn't have. A simple feature you would expect a reporting tool to have is the ability to search the repository for a report. It doesn't even have that capability. That's been a feature that we've been asking for since the beginning and it hasn't been implemented yet."
"A big problem after deploying something that we do in Lumada is with Git. You get a binary file to do a code review. So, if you need to do a review, you have to take pictures of the screen to show each step. That is the biggest bug if you are using Git."
"I would like to see more improvements with AS400 DB2."
"Lumada could have more native connectors with other vendors, such as Google BigQuery, Microsoft OneDrive, Jira systems, and Facebook or Instagram. We would like to gather data from modern platforms using Lumada, which is a better approach. As a comparison, if you open Power BI to retrieve data, then you can get data from many vendors with cloud-native connectors, such as Azure, AWS, Google BigQuery, and Athena Redshift. Lumada should have more native connectors to help us and facilitate our job in gathering information from these new modern infrastructures and tools."
"I would like to see support for some additional cloud sources. It doesn't support Azure, for example. I was trying to do a PoC with Azure the other day but it seems they don't support it."
"If you develop it on MacBook, it'll be quite a hassle."
More Pentaho Data Integration and Analytics Pricing and Cost Advice →
Earn 20 points
CloverETL is ranked 61st in Data Integration while Pentaho Data Integration and Analytics is ranked 15th in Data Integration with 48 reviews. CloverETL is rated 7.0, while Pentaho Data Integration and Analytics is rated 8.0. The top reviewer of CloverETL writes "Provides wealth of pre-defined, customizable components, and descriptive logging for errors". On the other hand, the top reviewer of Pentaho Data Integration and Analytics writes "It's flexible and can do almost anything I want it to do". CloverETL is most compared with SSIS, Talend Open Studio and iWay Universal Adapter Framework, whereas Pentaho Data Integration and Analytics is most compared with SSIS, Azure Data Factory, Talend Open Studio, Oracle Data Integrator (ODI) and AWS Glue. See our CloverETL vs. Pentaho Data Integration and Analytics report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
