On February 13th, 2020, Chartio will be updating all Redshift connections to the latest Amazon driver (v. 220.127.116.110) provided by Amazon. We were excited to find that in our early testing with beta customers, we’ve observed a reduction in query time by as much as 3 seconds per chart.
As a part of this performance improvement, Redshift will now use temporary tables automatically when doing subqueries. To allow for this, we’ve removed the “Read Only” connection option for any Redshift data source (found in the Connection tab of your data source in Chartio).
What changes are needed?
It’s likely no change is needed, but we recommend checking your permissions for your Chartio Redshift user. Your user will need the ability to create temp tables. Most user connections will have this access by default, but if it’s been revoked, Redshift may throw an error on subqueries that attempt to create a temp table.
If access to create temp tables has been revoked, you can update your permissions by following the instructions in the AWS documentation.
If you have any additional questions, please reach out to us at email@example.com.
Will my user lose read only access when you make this change?
While we’ve removed the “Read Only” option on Redshift data sources, we still restrict certain commands directly in Chartio, and you have complete control over the permissions you grant Chartio.
How do I know if my Redshift user has temp table permissions?
The ability to create temp tables is defaulted to “on” for all users in the PUBLIC group. So unless you’ve explicitly revoked temp table privileges from the user or their group, you won’t need to make any changes.
From the AWS Documentation: