We have been using Cascading framework for creating ETL.
Cascading gives.
Now we have two options converting some X ETL(which is costly) jobs into hadoop jobs
My question is.
converting X ETL to cascading workflows will require to create all the components available in the given X ETL, but will be one time activity. Then we need to think on other feature also which are provided by Talend Studio like:
a. Data quality. b. Data Profiling. c. Data lineage, etc.
Bottom line is I am creating a conversion tool from X ETL to hadoop jobs. And I need to choose from Cascading framework or Talend.
I cant't answer all your question but i can give you my return on experience. With Talend development is most productive than From wark or native language , and source is most easy to maintain because component are optimized and the IDE for your Job is very clear . The debuging features are good , you can do step bu step debugging and you can the your generate sources.
For me the inconvenients are the configuration management , Talend is not very successful to work with many branchs.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.