-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add "timestamp without time zone" as supported data type #35
Comments
@pcorbel does Currently, the thinking is that the only supported tables are those that the |
@AlexanderMann I agree that only supported tables are those that the We can't have:
But only:
|
@pcorbel do you know whether you're getting these errors on just running the ie, is it:
I ask, because I think the guidance has been that The reason for this is that the stores a tonne of metadata into the remote table's |
@AlexanderMann It is the 1 case you mentioned. |
Fascinating. So @pcorbel to be clear, you are not looking to mix and match maintenance of tables between If yes, I think we should identify where the code is blowing up by pulling in other stuffs first, as I can easily see this becoming a game of whack-a-mole with types etc. |
Amazon Redshift has a data type "timestamp without time zone" which isn't supported by the target yet (only "timestamp with time zone" is supported via target-postgres)
Source: https://docs.aws.amazon.com/redshift/latest/dg/c_Supported_data_types.html
So when target-redshift scan the destination schema, the following error occurs:
The text was updated successfully, but these errors were encountered: