MySQL to Snowflake: NULL result in a non-nullable column

[Chitrangad]

Hello,

I'm running into a peculiar issue.

I have a simple job that reads from MySQL and loads into Snowflake via Bulkexec with a tMap in between. I have auto-type conversion enabled.

All the fields in both source and target are not-nullable and data also doesn't have any nulls.

However, I keep getting this error message when trying to run. Oddly enough, it comes for the 1st field which is a primary key. I tried null handling but no luck.

"NULL result in a non-nullable column"

Appreciate if someone can help with the issue?

[Anonymous]

How do you handle null value?

For debugging, try to use tLogRow to print the value on the console or use tFilterRow to filter the null value to check there exist null value.

Regards

Shong

[Chitrangad]

Hi,

I'm using row1.column==null?"":row1.column

Checked the data visually (12 recs) as well as by adding a reject file. There are no nulls.

[Anonymous]

Take a look at this topic and check if you have similar cause.

https://community.talend.com/s/question/0D53p00007vCp6xCAC/null-result-in-a-nonnullable-column-error-while-inserting-data-from-one-snowflake-table-to-other-snowflake-table-using-talend-data-integration

[CFlores1613722497]

Check the Default value status for column (PK) in table structure.

Sequence in the table(PK default value) will be in invalid state if sequence is dropped and recreated/replaced with same name after creating table. drop and recreate the table again. Check the sequence status and load the data. shareit vidmate