Forum Discussion
Incoming mapper upstream has combination of numbers sample like 47577 & 595546349.04. I have 3 mapper snaps followed by bilk load. Before these 3 mapper I have csv parser snap as I am reading google sheet. In 1st & 2nd mapper input schema is string, target schema is any for both mapper. 3rd mapper input schema is string and target schema is integer. I have removed all the parseFloat() or trim() expression from my pipeline and having double precision in create table. Still I am getting same error while validation with same message shared before.
Not sure why!
Regards,
Amar.
The error you are receiving is from the Redshift database trying to insert a decimal into an integer field. Can you tell me the data type of the annual_revenue field ? It seems it is defined as an integer, but we’re trying to store a decimal number into field. So all the snap data transformation, etc, are relevant, but what really matters is the final value getting inserted into the target database, and it seems there is a mismatch here.
Here is some sql to emit schema for a table. I’m sure there are other ways in Redshift.
SELECT "tablename", "column", "type" FROM PG_TABLE_DEF WHERE schemaname = 'public' AND tablename = 't1207' -> TABLENAME COLUMN TYPE t1207 id integer t1207 bigdecimal double precision