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
Hi,
It is welcome to open a feature jira issue of DI project for your requirement on
Talend Bug Tracker.
For tNetezzaInput, the dynamic type support is there, not tNetezzaNzLoad, tNetezzaOutput.
Best regards
Sabrina
You can use dynamic schemas to read from other DB's and write to a file(which supports dynamic schemas) then use nzload. If you need to source files dynamically from NZ use CREATE EXTERNAL TABLE to create the files.
Hi,
It is welcome to open a feature jira issue of DI project for your requirement on
Talend Bug Tracker.
For tNetezzaInput, the dynamic type support is there, not tNetezzaNzLoad, tNetezzaOutput.
Best regards
Sabrina
Hi jan.fabian,
Could you please paste the feature jira url on forum so that other community can check it. Thanks for your contribution.
Bets regards
Sabrina
Hi, thank you. The workaround proposed by jholman works with two significant drawbacks: it is slower and I cannot create table if not exists while loading data into Netezza. Best Jan
I have found create external table to be quite fast and even faster than any other method if using COMPRESS TRUE when moving between Netezza NPS. Also, Netezza does not support IF (NOT) EXISTS statements, so you cannot use that anyway. I usually query the catalog table _V_TABLE to see if the table exists and drop it if required (or write an SP).
My problem is related to the tNetezzaOutput, so I need to load data with dynamic schema into Netezza. Writing to a file and SCPing it to a DB server is slower than just using tNetezzaOutput. And anyway, it is a solution that is not suitable for us, compared to using talend components for inserting data into DB.
With the create table if not exist, I was talking again about the tNetezzaOutput component and the "action on table" - that works, actually. Sorry for not being clear.