Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are starting our adoption of Talend and, in general, it is much more robust that our current Informatica software, however there is some room for improvement. After working through the creation of my first production job, I have the following constructive feedback regarding Talend Studio:
24. If you copy and paste components instead of showing up near your cursor or near the copied component, it seemingly shows up in a random potentially off-screen location and needs to be tracked down.
25. If you copy a group of components with a tMap in the middle and change the schemas on either side and resync etc., no matter what, the tMap will not let go of the older columns and simply needs to be deleted and recreated.
26. There is no notification component and instead a warning component must be used instead to signify the end of the job and pass an exit/return code. Warning should not be the standard for this. Something like tUpdateJobStatus or tExitCode should exist.
27. Running steps should be highlighted. It is hard to tell which step is currently processing when testing.
21 . you could use filter expression of tMap multiple outputs.
14.just presse f1 on a field of a component it will redirect you to the documentation of the component.
22.If you use studio version : tParallelize or tPartitioner else you have other way to make parallelization in open studio.
26.there is an internal variable ExitCode also you can write directly in the console with just few line of java.
3.in the Outline view you can see a full view of your job and navigate more easily in.
28.Like every tool Talend have limitations but as far i know it's one of the most powerfull and robust. Just keep to dig in you 'll see you could do a lot of thing with.
Hi @Not defined Not defined,
Thanks for raising this feedback. There is some very interesting content in there. I COMPLETELY understand some of the points you raise (the first 4 being frustrations I have had in the past). There are also a couple of points where I feel I can offer advice or a workaround. Naturally, I will pass all of this on to our R&D team, but let me see if I can help with some of the issues....
For number 6 you will get far more info from the Code tab (bottom left of the developer canvass). If you ever get errors with components which show up as a red box, this is the first place you should look. They will more than likely be Java compilation errors caused by parameters of components not having been filled in properly. It is always a good idea to look at the code tab and check for red blocks on the right to identify potential config errors before you try to run/build as well.
I'm not sure about point 7, but let me try to explain how to resolve the line numbers frustration. When you click on your code tab, you will see the code that has been autogenerated by the placement and configuration of components. You cannot edit this code, it is just so that you can see what is happening. Sometimes you may notice that the line numbers are not present. To switch these on, right click on the thin grey line down the left side of code screen and you will see a box like this....
Simply select "Show line numbers" and they will appear.
For number 8, I can see what you mean. This doesn't work elegantly, but it does work if you click on the magnifying glass.
But there is a MUCH better way of finding a component that you may need, which is why I do not worry about the issue you raised here anymore (I used to). If you start typing the name of the component you want to use on the developer canvass, it will do exactly as you wish.....
Number 10 IS a pain. However, here is a workaround. If you have a Context named "BOB" and you want it changed to "bob", you can do this. First rename it to "BO" by deleting the final "B". Then overwrite it again with "bob". This will work. Yes, it is a pain, but this will work for you. As I said, I will raise this though.
For number 11, this can happen if you change the schema to be built-in. Also, with repository schemas you can find that the columns are made available, but are not switched on automatically. In some cases you may not want your job to automatically add columns which are switched on. This one can catch you out, I know.
I have to say I like your suggestion for 14. But if you click on the component and hit F1, it will load the help page you require. It's a bit like an Easter Egg 🙂 But I understand how this is not easy to find.
If I understand 16 correctly, yes, that can be a frustrating experience. There is a quick fix to this....
I'm not sure I understand 18. Can you elaborate on that for me? It doesn't ring any bells for me.
For 19, we are working on that as we speak. Multiple logins have built up during the lifespan of Talend and we are very aware of the issues caused. Since Talend has grown via organic growth and acquisition, it has been something that has happened without intention. As I said, this will be fixed.
I may be misunderstanding 20, but I don't see that issue. This might be because I am doing something different to what you are explaining, but let me show you my Snowflake version of this....
For 21, @guenneguez jeremy explains this, a tMap is what you want for this. There is a lot of crossover between a tMap and a filter. I tend to use the tMap in the majority of cases. The example you gave is perfectly handled by the tMap.
For 22, @guenneguez jeremy has also nailed this. I should add that the tPreJob and tPostJob components have very important uses. The tPreJob will fire before ANY of the rest of the job (even context variable settings) fire. So you can handle things like dynamic contexts there. The tPostJob is MUCH more significant. Sometimes when you are running a job it may fail due to an unexpected nullpointerexception or something that causes another Java runtime error. Without the tPostJob the job would just fail and end. With a tPostJob the job will fail, but the tPostJob will ALWAYS be fired. Therefore you can use it to clean up and/or catch errors. It's incredibly useful.
Number 23 is my fault. We used to have a section in the Community for this before we migrated to this platform. Unfortunately it was seldom used for the right purpose at all. We also realised that we were asking in two separate areas for Feature Suggestions. You can raise these in Jira (https://jira.talendforge.org/). First, you will need another login at the moment and you can find a page to register here (https://login.talend.com/login.php). Once you've registered you will need to login via the Jira URL I gave previously. I know, this is really not ideal to have to do this, but this WILL be fixed. It is just a matter of time I promise.
I couldn't recall having experienced 25, so I have tried it out according to your description. I *think* that maybe you are not updating the schema by pushing it back. These screenshots show what is required....
So, I deleted half of the components on the right, then clicked the double arrows pointing back (in the red box). This leaves you with this....
If you check your tMap, you will see that the columns have bee updated.
As I said, I am open to being shown I have misunderstood. I am also using a Mac and I know that sometimes there are differences between Mac and Windows versions (although I've only seen things struggling on Mac after a new Mac OS or update).
For 26 there are a plethora of ways to indicate the end of a job. As mentioned before, the tPostJob component is really useful for enabling you to ALWAYS call the end of a Job and to allow you to do whatever you like to indicate the end of a Job. I have used emails, database updates, SMS messages, Slack messages, .....I've even enabled my Google Home device to tell me a Job has completed in the past. One of the main benefits of Talend for me is that I can use ANY third party API with it. All I need is a bit of Java and an understanding of the API.
For running steps you can build these in with several components (tJava, tJavaFlex, tLogRow, etc), there is also Log4J. This tutorial/article might give you some pointers here....
https://community.talend.com/s/article/Log-j-tips-and-tricks-I8730
As I said, thanks so much for raising these points with us. While I have given a few workarounds, that is not to say that we do not need to look further into these areas. I will now be in touch with several other teams to highlight these points.
Regards
Richard
Hi @Not defined Not defined ,
Thanks for sharing your feedback.
For 13, I'm not sure I see what ribbon you're talking about; Feel free to paste a screenshot here or open a DOCT issue in JIRA, for us to look into this.
For 14., not intuitive but a workaround, press F1 on any component icon on the canvas should take you to the corresponding documentation (online). But definitely a good old question mark would make it more obvious.
For 15, we'll look into the cheat sheets issues (was this in the Data Profiling perspective? ).
For 19, we have an initiative to simplify the authentication throughout the whole Talend ecosystem. As all what touches sign-in and identity management, this is not a simple topic. But we hear you.
Thanks again for the feedback.
Elisa
Head of Documentation & i18n
Thanks! These were all very helpful. #14 and #3 are going to save me a lot of time going forward. I just wish that there were more options to better organize the Designer objects automatically like Informatica has. A lot of time was wasted to trying to get lines to not overlap object and the things to be organized cleanly.
for designer, you'll see with the time you can organize thing pretty clearly, could you send an example of line overlap object , i'm very curious about that
cause you can organize the layers of subjob and components for example you can right click on an empty area of a subjob and then you have options like bring to front or bring to back
in the palette you can also right click on component you use a lot and set it as a favorite,
it will be shown in the first folder of the palette
Hi @Elisabeth Sabot ,
Thanks for your response.
13. Before submitting a bug report. I am simply trying to hide the following toolbar. It looks like it will only let me move it:
If you go to Exchange, there is only a very limited list of about 26 components. There is no next page button. Is this accurate?
15. I'm in the Integration perspective. Here's what happens:
Please also note, this forum allows me to copy and paste images from the Windows clipboard into the editor, such as through the Snipping Tool, but then it drops those images when submitted. Very frustrating. I had to go back in and save each image as a file and upload then one-by-one.
I'd like to be able to drag the line itself around like I would in a tool like Vizio
vs. having to move the last object in the line a little down.
you don't need to use an onsubjob ok link after the component wich finish the prejob line, the tprejob line will be executed before everything else (it's it purpose)
after this in general when you work with subjob you will use the on subjob ok link between the first component of each subjob (it was designed to avoid z pattern).
Between simple components like dbconnection (use on component ok instead of on subjob ok).
Send me Love and kudos