-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot parse timestamp type #86
Comments
Hi @HaydenNess , You will need to provide a lot more context to help diagnosis this issue please. A definition for the table in question, and what is likely the column with the error i.e. the date-time column. This is the definition for what could be date-time columns. It would be good if you could show, what is the value in the source system (which is failing for that row), version of SQL Server, and definition for the column that is failing. Another possibility is that the definition for the CDC table is out of sync with the main table i.e. the main table has had a definition change but the CDC table has a different definition because it was not synchronised across. If it is that problem, read this page for more details about CDC table changes - https://github.com/wintersrd/pipelinewise-tap-mssql/blob/master/MS_CDC_SETUP.md |
Thanks Hayden, I work with @s7clarke10 - the problem is that we haven't encountered any cases where our source data contains columns of TIMESTAMP (or ROWVERSION) data type. Would you be able to test an update to tap-mssql where you move TIMESTAMP out of the I suggest altering this section: |
I have attempted a fix, treating TIMESTAMP values as strings but converting them to BIGINT when performing the comparison for an incremental replication |
Moving 'timestamp' to the STRING_TYPES list indeed works, so that's an easy fix I can apply in the meantime. It would be preferable to have as an integer type, as you seem to be working on, for space and performance reasons though. Thanks! |
I'm posting a copy of the issue meltano/sdk#2711 to here.
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.
The text was updated successfully, but these errors were encountered: