Thanks, but here is my argument that they may not be seen as different
purpose: I am thinking both Redshift and Hive as a data warehousing
solutions, with STS as a mechanism to lift hive's performance (if Tez or
LLAP can provide similar performance, I am fine to use Hive Thrift Server
So, I want to build and implement core DWH models (read star schema) on
Hive and expose it through some non-mapreduce framework.
Does that make sense? Or I am thinking in wrong path and Redshift can do
On Fri, Sep 23, 2016 at 4:18 PM, Jörn Franke <jornfra...@gmail.com> wrote:
> Depends what your use case is. A generic benchmark does not make sense,
> because they are different technologies for different purposes.
> On 23 Sep 2016, at 06:09, ayan guha <guha.a...@gmail.com> wrote:
> Is there any benchmark or point of view in terms of pros and cons between
> AWS Redshift vs Spark SQL through STS?
> Best Regards,
> Ayan Guha