DSXchange

Hi,

Job failed with nullability issue in funnel. though two source columns are defined as nulls in the ETL from beginning to end.
fyi. table1.col1 -null ; table2.col1 -not null where as metadata is null in both ETL source tables

job runs fine if I create a temp table(table2) with col1 as null.
I did workaround by using a Union instead of funnel to avoid nullability issue.

question is why funnel is aborting the job though metadata is same.

thank you,
Have a Great LONG[Short] Weekend!
Kiran[/img]

Post your actual, complete, unedited error messages. And what matters is what the source/target actually say re: nullability, not how you declare the columns in the job.

Chulett,

Here is the Error Message..
main_program: When preparing operator: When setting up transfer or "Status_dt":The source and destination have differing nullability.

Then cause them both (all) to have the same nullability - either both (all) nullable or both (all) not nullable.