Redshift Spectrum Vs Athena. Athena stores query results on S3 and they can be loaded into Redshift from there. However Redshift Spectrum tables do also support other storage formats ie. Because Redshift Spectrum and Athena both use the AWS Glue Data Catalog we could use the Athena client to add the partition to the table. Data Storage Formats Supported by Redshift and Athena.
Another is the availability of GIS functions that Athena has and also lambdas which do come in handy sometimes. Amazon Redshift has a broader approval being mentioned in 270 company stacks. On the other hand Athena supports a large number of storage formats ie. Using decimal proved to be more challenging than we expected as it seems that Redshift Spectrum and Spark use them differently. Spectrum requires a SQL client and a cluster to run on both of which are provided functionality by Amazon Redshift. The actual real world performance of Athena vs.
Parquet orc avro json etc.
Using decimal proved to be more challenging than we expected as it seems that Redshift Spectrum and Spark use them differently. With Redshift Spectrum you have control over resource provisioning while in the case of Athena AWS allocates resources automatically. 1972019 Amazon Redshift Spectrum. The comparison of Amazon Redshift spectrum vs Athena leads to an interesting outcome in terms of pricing. An analyst that already works with Redshift will benefit most from Redshift Spectrum because it can quickly access data in the cluster and extend out to infrequently accessed external tables in S3. Athena supports it for both JSON and Parquet file formats while Redshift Spectrum only accepts flat data.