What we really need in Talend OS

navds — Sat, 16 Nov 2024 08:24:43 GMT

Hi all,

I've been working with Talend Open Studio DI/ESB for a few months now. Here is, what I think, is frustratingly lacking. Maybe, it's due to my own misunderstanding or just by design; anyway I'd like to hear your opinions.

Custom object returned by a tBufferOutput. So far, we do it by mediation of a routine. I simply don't understand why we can't .
tMap with processing following output link order. I learnt it the hard way, surprisingly the order of a tMap outputs is meaningless . It would be very useful to have the ability to control which operations run after which.
Better extensibility. Custom components are good, exchanging them in talendforge is awesome but what if we have plugins management system ?
Improved version control system. Sometimes routines get complicated enough to manage, I am sure some of you write them in external editor/IDE to keep track of modifications, like I do.
Package repository integration. In 2018, we still select every jar one by one to be included in routine dependency or invoked by a tLibrary load. Life would be sweeter if we can use gradle or simply a working dependency management system which can download them and setup class paths automatically.
Smoother and nicer interface. GUI are important since it's the materialization of every good concepts behind any software. There are a lot of lost space in the graphical interface of current version (I'm on version 6 at this writing). Write some codes in a tJavaFlex and you'll realize what I mean. At first sight at the whole window, you'll notice that more than 25% of elements are distracting and restricting actual productivity. Also, a functional dark theme is very welcomed. Community will be glad to contribute if point (3) is checked.

Re: What we really need in Talend OS

Anonymous — Fri, 13 Apr 2018 15:23:01 GMT

@navdswrote:

Hi all,

I've been working with Talend Open Studio DI/ESB for a few months now. Here is, what I think, is frustratingly lacking. Maybe, it's due to my own misunderstanding or just by design; anyway I'd like to hear your opinions.

Custom object returned by a tBufferOutput. So far, we do it by mediation of a routine. I simply don't understand why we can't .
Return your custom object as an Object and use Java casting to covert to and from.

tMap with processing following output link order. I learnt it the hard way, surprisingly the order of a tMap outputs is meaningless . It would be very useful to have the ability to control which operations run after which.

The output link order is followed, but per row. If you want an order to be maintained you can order the data going into a tMap

Better extensibility. Custom components are good, exchanging them in talendforge is awesome but what if we have plugins management system ?

You can extend Talend better than ANY other data integration tool. You just need to use Java. But you can make use of ANY third party Java API and ANY web service API as well as using someone else's components. The limitations of extending Talend are set by the user.

Improved version control system. Sometimes routines get complicated enough to manage, I am sure some of you write them in external editor/IDE to keep track of modifications, like I do.

The Enterprise Edition deals with this, but it is still not what I would call perfect. You can quite easily make use of GIT or SVN for this though.

Package repository integration. In 2018, we still select every jar one by one to be included in routine dependency or invoked by a tLibrary load. Life would be sweeter if we can use gradle or simply a working dependency management system which can download them and setup class paths automatically.

I may have misunderstood your problem here, but I believe this is covered by the Enterprise Integration with Sonatype Nexus.

Smoother and nicer interface. GUI are important since it's the materialization of every good concepts behind any software. There are a lot of lost space in the graphical interface of current version (I'm on version 6 at this writing). Write some codes in a tJavaFlex and you'll realize what I mean. At first sight at the whole window, you'll notice that more than 25% of elements are distracting and restricting actual productivity. Also, a functional dark theme is very welcomed. Community will be glad to contribute if point (3) is checked.

I kind of agree here, but there are ways to work around this. My Studio is configured very differently to many other people I have worked with. I tend resize areas that are not used much by me in order to maximise the space for areas I use a lot. While you can work around this frustration, it would nice if it could be thought about. This might be limitation of Talend using Eclipse though.

topic What we really need in Talend OS in Talend Studio

What we really need in Talend OS

Re: What we really need in Talend OS