it does take a bit of time to open it.
1. Make tMap sort aware. So if lookup is sorted on join keys and if tMap knows it, it can do the joins more efficiently as it does not have to go to the end of the table each time.
2. Make it able to handle large data sets easier. I've had errors when I had a lookup table as big as 200K rows. I got some NetBeanLookup error (I do not remember exact error). It was almost like an Out of Memory error. I was able to get around by making the table as skinny as possible. This was when I was caching it on disk (not in-memory). This is critical.
3. A scroll bar for large tables inside will be great.
Ability to directly lookup DB tables. If we have a million row table (which is not even that big), why spool all the rows to disk? Based on my observation, TOS is going to fail (at least in Java). Why not add ability to directly connect to the database table and do a lookup? Do we have this functionality in some other component?
In disk mode, data are sorted on the result of the keys expressions
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema