The goal of this board is to provide an area for sharing the how to's many of our members end up writing when replying to questions on the other boards. It has been an ask from the community that we provide an area that could be used to curate this content and insulate it from the Q&A flow we see on other boards, so here we are.
For starters, there's nothing better than writing once and linking everywhere. Additionally, it provides great visibility and makes it easier to collect those kudos. The team and I will be watching this board for content that could be used on the Talend Blogs, Webinars, possibly even a speaking session at @ Talend Connect; we want to highlight the luminaries within this community and this board is the first start.
You might also see contests in the future where authors of content here will automatically be entered to win so it doesn't matter when you post, just that you did.
I am a firm believer that knowledge is only useful when it's shared, I look forward to reading your posts.
Chief Evangelist @talend
Kudos for this! and appreciate the effort...
These wonderful examples and how to's, but they (9 out of 10 times) focus on just doing the job, in example: reading multiple files, et voila it works and everybody's chearing ... just by reading the docs you get there... But it's about exceptions, common errors, encoding mistakes, etc. If you want to speed up the learning-curve add these kind of links : common issues / errors . My suggestion would be there's always a Talend suggested solution which is linked to expert user and accompanied with the ability to download examples and maybe even full templates.
Next thing... improvement in components to make dev-life easier.
When working in production/business environments there's a call for a high level of flexibility and parameter driven jobs.
I have to say when looking and working with tools like NiFi the way things are designed in Talend are becoming 'outdated' , especially provenance and logging are not made intuitive / easy. Passing data through jobs and access response on the parent or child job ...
In example, calling https - rest api's with oAuth2 security/authentication where you need to retrieve huge amounts of data and a token-expiration set 3600 seconds.
Would be nice if these examples are accompanied with a test server ... so you are able to run a job against talend educational environment.
We all get (quick) to the point where advanced/expert user knowledge is needed to get advice based on best and next-practices... not the read the f#ck/ng manual stuff ! I don't like the gamification / rewarding points stuff idea. The incentive should be a bit more sophisticated... But hey it's a first step to improve community collaboration!