"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"It is really easy to set up and the interface is easy to use."
"In StreamSets, everything is in one place."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"Integration with all systems is easy with Oracle Data Integrator, and it is easy to use. I have not used any other product, but with Oracle Data Integrator, we can easily connect to an ERP system, an SAP system, or a cloud application."
"ODI's most valuable features are it utilizes the database engine and is very lightweight."
"Oracle provides great documentation."
"The most valuable features of ODI are the ease of development, you can have a template, and you can onboard transfer very quickly. There's a lot of knowledge modules available that we can use. If you want to connect, for example, a Sibyl, SQL, Oracle, or different products, we don't have to develop them from scratch. They are available, but if it's not, we can go into the marketplace and see if there's a connector there. Having the connector available reduces the amount of hard work needed. We only have to put the inputs and outputs. In some of the products, we use there is already integration available for ODI, which is helpful."
"Easy to understand, very developer-friendly, and has a big forum community and lots of documentation for support."
"The scalability is great. It's one of the reasons we chose the solution."
"The most valuable features of Talend Open Studio are customization and integration."
"It is user-friendly and the interface is good."
"The most valuable features are definitely data integration, data preparation, and data stewardship."
"Talend is safe to use because it is very restrictive. It is easy to use when one learns how to manipulate data with SQL."
"The most valuable features are the ETL tools."
"It has got so many connectors. It is intuitive and easy to use."
"A very user friendly solution."
"Talend can connect to multiple data sources, including relational data sources, ERP, CRM, and others."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"ODI could improve by being more user-friendly. Informatica, which is also an ETL tool, similar to ODI, but Informatica is very user-friendly, easy to use, and simple to integrate, compared to ODI. ODI has many features, put them all together, and sometimes we get confused about which ones to use, which ones not to use."
"It has been very good. Just recently, I've faced an issue, but I solved it somehow. While integrating with a file, I faced an issue where I wanted output files, and I had used the text field limited quotations, but at the end of the file, there was a line breakage for the last column. So, we just removed the text field because it was not working correctly for us."
"The resource management aspect of the solution could be improved."
"An area for improvement would be the lack of SQL compatibility - ODI has no ability to interact with SQL unstructured types and data types."
"The solution lacks some functions and features."
"The interface of ODI could be improved. For example, navigating and finding functions can be difficult. For example, you have to know which step you need to go to look at where your job status is. The logical step is a bit complex compared to other tools. It's much easier to get a graphical view, but with ODI, it's graphical, plus you have to know all the other pieces that fit around it. You have to think about the logical and physical aspects."
"Talend should improve the log and error handling to better track the errors you find during development. Sometimes it's challenging to see what's causing an issue, and tracking that on Talend is complicated."
"The security features could be improved."
"It is not as visually appealing as some of the other tools."
"It doesn't have the ability to keep the repository of the source code (visual pipeline). It can be integrated with Git."
"he overall marketing and documentation of this product need to improve a lot."
"Talent consumes a lot of resources on my PC."
"The product could be more intuitive."
"As for improvement or additional features, I would like to know how to use Java in Talend and also how to use Talend in the cloud or in big data. I would prefer to have storage directly on Talend."
Oracle Data Integrator (ODI) is ranked 6th in Data Integration Tools with 8 reviews while Talend Open Studio is ranked 4th in Data Integration Tools with 18 reviews. Oracle Data Integrator (ODI) is rated 8.4, while Talend Open Studio is rated 7.8. The top reviewer of Oracle Data Integrator (ODI) writes "We can make all the EPM tools work together as one and we can create a puzzle that will increase the performance and capability of all EPM tools". On the other hand, the top reviewer of Talend Open Studio writes "Popular open-source ETL tool in Singapore/ South East Asia; Connects to Big Data; Easy to spot errors with generated Java code". Oracle Data Integrator (ODI) is most compared with Oracle Integration Cloud Service, SSIS, Informatica PowerCenter, Oracle GoldenGate and Azure Data Factory, whereas Talend Open Studio is most compared with SSIS, AWS Glue, Azure Data Factory, Talend Data Fabric and Hitachi Lumada Data Integration. See our Oracle Data Integrator (ODI) vs. Talend Open Studio report.
See our list of best Data Integration Tools vendors and best Cloud Data Integration vendors.
We monitor all Data Integration Tools 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.
