Redshift Spectrum – Exabyte-Scale In-Place Queries of S3 Data

Re:Redshift Spectrum – Exabyte-Scale In-Place Queries of S3 ... by georgewfraser on Wednesday April 19, 2017 @02:36PM (#14150460)

This appears to be Amazon Athena / Presto, embedded into Redshift. The syntax for CREATE EXTERNAL TABLE is exactly the same, and the supported file formats and compression encodings are a subset of Athena. The big advantage of an approach like this versus running Redshift and Athena separately is that you can write a single query that joins data stored in Redshift with data stored in Athena.

[ Parent | on HN ]

Re:Redshift Spectrum – Exabyte-Scale In-Place Queries of S3 ... by idunno246 on Wednesday April 19, 2017 @02:50PM (#14150596)

And you can actually materialize a query in redshift since Athena doesn't have create table as select. This is neat, though I wonder if opening Athena to connect to Postgres(presto can) and do the join inside Athena would have been better

[ Parent | on HN ]

Re:Redshift Spectrum – Exabyte-Scale In-Place Queries of S3 ... by openasocket on Wednesday April 19, 2017 @03:35PM (#14151001)

I'd say that I have more confidence in the Redshift query planner and execution engine than that of presto. And having the option to join that with data stored in-memory on redshift nodes is very attractive.

[ Parent | on HN ]

Re:Redshift Spectrum – Exabyte-Scale In-Place Queries of S3 ... by vhold on Wednesday April 19, 2017 @05:55PM (#14152162)

It's also the exact same cost, $5 per terabyte read.

[ Parent | on HN ]

Re:Redshift Spectrum – Exabyte-Scale In-Place Queries of S3 ... by awgupta on Thursday April 20, 2017 @11:19AM (#14157451)

The underlying tech stacks are totally different.

[ Parent | on HN ]