-
Notifications
You must be signed in to change notification settings - Fork 65
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
Fix base_source_columns
and base_node_columns
in Redshift
#467
Fix base_source_columns
and base_node_columns
in Redshift
#467
Conversation
type_large_string()
and consolidate schemas for base column modelsbase_source_columns
and base_nodel_columns
in Redshift
base_source_columns
and base_nodel_columns
in Redshiftbase_source_columns
and base_node_columns
in Redshift
Thanks for the work on this one! At first, I am a bit worried of moving to From what I read here , I understand that Redshift does some optimization/memory allocation based on the types and I wouldn't want people who don't have any issue today with Redshift to be negatively impacted by performance following this change. In your specific case, do you know what specific column(s) was/were creating the issue? And what We might then be able to target the changes required to fix the reported issues. |
Hey @b-per For some reason, However, I'm still running into issues with So maybe we bump the |
Yes, I think it is better to get to the bottom of it. Do you have
and copy the results here? My results look like
|
Hey @b-per , here are the results from the
|
With #475 implemented and released in the latest version, I think that this is not needed anymore. Let's open a new issue if there is still an issue. |
This is a:
Link to Issue
base_source_columns
#465base_source_columns
andbase_node_columns
in Redshift #466Description & motivation
base_source_columns
andbase_node_columns
in Redshift #466type_large_string()
inbase_source_columns
andbase_node_columns
redshift__type_large_string
lengthinsert
errorIntegration Test Screenshot
Checklist