amazon-redshift-utils icon indicating copy to clipboard operation
amazon-redshift-utils copied to clipboard

Amazon Redshift Utils contains utilities, scripts and view which are useful in a Redshift environment

Results 62 amazon-redshift-utils issues
Sort by recently updated
recently updated
newest added

Hi, we are currently migrating some external tables into a new database and rely on the admin view `v_generate_external_tbl_ddl` to reconstruct the DDL. However, in some cases it seems that...

Hello team, I'm getting the following error when I execute the SystemTablePersistence lambda utility: ERROR] ProgrammingError: {'S': 'ERROR', 'C': 'XX000', 'M': 'Value too long for character type', 'D': '\n -----------------------------------------------\n...

I'm trying to drop a group from my redshift cluster. Using the latest version of v_generate_user_grant_revoke_ddl, I'm running the following query to get the DDL statements to run for the...

*Issue #714 Installing requirements.txt on Ubuntu 22.04 with default python 3.10.12 fails with a conflicts between redshift-connector and boto3.

Hey fellas. Installing requirements.txt on Ubuntu 22.04 with default python 3.10.12 fails with a conflicts between redshift-connector and boto3. How to reproduce it: * Start a fresh Ubuntu 22.04 ec2...

Hi Team, I am currently using this DDL, It is kind of incomplete without specifying the complete return type. right now it returns either character, date or numeric but my...

Latest version of the script generates SQL "REVOKE ALL ON DATABASE ..." on datashares which is invalid syntax. Can this get updated to support datashares?

*Description of changes:* Add view AdminViews: *v_get_running_queries* This view will show all current queries in the cluster, ordering it by the start execution date. By submitting this pull request, I...

The output of the v_generate_user_grant_revoke_ddl creates invalid statement because it quotes the object. ALTER DEFAULT PRIVILEGES for user testuser in schema testschema REVOKE ALL on "tables" FROM testone; ALTER DEFAULT...

*Issue #, if available:* #707 *Description of changes:* Add schema to the join condition when getting column comments to avoid getting column comments on table with same name from another...