Is there any solution for this? I have to load 3 times the date and hour tables !!! |
Im tMap, you can create a lookup based on the same table more than once, but, essentially, you are incurring the extra memory for each duplicated lookup table, nit to mention cluttering up the job display . Also, if the solution adds inferred dimension members on the fly, and that dimension is on eof the dups, then I would doubt that the others would get get updated. - not sure if Talend dynamically updates lookup cache as records are added.
I am used to SSIS (I like Talend better), where the same lookup table can be aliased several times. Also, added inferred dimension members are dynamically added to the lookup cache as well.
Hopefully talend will jump on this one.
Dave