Skip to content

Conversation

@JoshRosen
Copy link
Contributor

Redshift throws extremely confusing errors when the Redshift cluster and S3 bucket are in different AWS regions. This patch expands the documentation to discuss how to fix these errors and adds logic to attempt to automatically detect and warn users when this case occurs.

Fixes #87.

@JoshRosen JoshRosen added this to the 2.1.0 milestone Oct 19, 2016
@codecov-io
Copy link

codecov-io commented Oct 19, 2016

Current coverage is 88.23% (diff: 68.00%)

Merging #285 into master will decrease coverage by 0.77%

@@             master       #285   diff @@
==========================================
  Files            12         12          
  Lines           655        680    +25   
  Methods         526        545    +19   
  Messages          0          0          
  Branches        129        135     +6   
==========================================
+ Hits            583        600    +17   
- Misses           72         80     +8   
  Partials          0          0          

Powered by Codecov. Last update bdf4462...b3bdff0

@JoshRosen
Copy link
Contributor Author

Going to merge this into master.

@JoshRosen JoshRosen closed this in d508d3e Oct 20, 2016
@JoshRosen JoshRosen deleted the cross-region-s3 branch October 20, 2016 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add configurations to allow tempdir and Redshift cluster to be in different AWS regions

3 participants