Using SQL statements vs. SchemaRDD methods

2014-11-04 Thread SK
SchemaRDD  supports some of the SQL-like functionality like groupBy(),
distinct(), select(). However, SparkSQL also supports SQL statements which
provide this functionality. In terms of future support and performance, is
it better to use SQL statements or the SchemaRDD methods that provide
equivalent functionality? 

thanks



--
View this message in context: 
http://apache-spark-user-list.1001560.n3.nabble.com/Using-SQL-statements-vs-SchemaRDD-methods-tp18124.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
For additional commands, e-mail: user-h...@spark.apache.org



Re: Using SQL statements vs. SchemaRDD methods

2014-11-04 Thread Michael Armbrust
They both compile down to the same logical plans so the performance of
running the query should be the same.  The Scala DSL uses a lot of Scala
magic and thus is experimental where as HiveQL is pretty set in stone.

On Tue, Nov 4, 2014 at 5:22 PM, SK skrishna...@gmail.com wrote:

 SchemaRDD  supports some of the SQL-like functionality like groupBy(),
 distinct(), select(). However, SparkSQL also supports SQL statements which
 provide this functionality. In terms of future support and performance, is
 it better to use SQL statements or the SchemaRDD methods that provide
 equivalent functionality?

 thanks



 --
 View this message in context:
 http://apache-spark-user-list.1001560.n3.nabble.com/Using-SQL-statements-vs-SchemaRDD-methods-tp18124.html
 Sent from the Apache Spark User List mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
 For additional commands, e-mail: user-h...@spark.apache.org