Hello,
I would really appreciate for my jobs, if I could use dynamic schema for Netezza components. However, currently, this is unsupported. I have found a similar topic here:
http://www.talendforge.org/forum/viewtopic.php?pid=57674 Is it planned to implement this feature or would it make sense to put a feature request at jira?
Thanks
Jan
I feel your pain on no dynamic schema support, I would love to have it for tNetezzaNzload especially, but why SCP the file?
You can just create the external table and load it from where it was created with nzload which outperforms JDBC easily, especially if they are compressed. eg:
tNetezzaRow (CREATE EXTERNAL TABLE) --> tNetezzaNzload
I know this doesn't help with table creation but will be much faster than tNetezzaOutput.
Well, that might work, thanks for the suggestion. Unfortunately, we are trying to get rid of any dumps into files, so I am not sure if this will be suitable. Anyway, closely related question: In the Talend Components Reference Guide on p. 1834, it is written for tJDBCOutput that it supports dynamic schema. This might be a solution for us, even when the JDBC component version is a little bit slower. However, when I check my supportDynamic.txt, tJDBCOutput isn't listed and it also really doesn't work for me. So is there a mistake in the reference guide?
Anyway, closely related question: In the Talend Components Reference Guide on p. 1834, it is written for tJDBCOutput that it supports dynamic schema. This might be a solution for us, even when the JDBC component version is a little bit slower. However, when I check my supportDynamic.txt, tJDBCOutput isn't listed and it also really doesn't work for me. So is there a mistake in the reference guide?
