Open HaydenNess opened 1 day ago
Hi @HaydenNess!
I think the SQL server tap may be at fault here, since it's declaring 0000000000004651
as a date-time
string. The error is coming from https://github.com/meltano/sdk/blob/bf8384eb830ddc852bcbee43f3534f734fb79751/singer_sdk/sinks/core.py#L559
letting it go through is probably not a good option either, but I'm not sure if pyarrow would complain that it isn't a valid datetime.
Can you try using Meltano's schema
override to change the type of that updated
field to something that better reflects its type? Maybe integer
.
Hi Edgar,
I've tried the schema override with, in various ways, without any success. It's unclear to me though if it is doing anything at all, or just doesn't affect the result.
I'll post this over to tap-mssql and see if it can be addressed there.
When trying to sync (CDC in my case) a table containing a 'timestamp' column, the following error is presented. I have experienced this with both target-parquet, and target-s3.
This error can be avoided by excluding the column from the select list, but the type is often vital to enabling incremental replication.