> but this sounds to me (without testing myself) adding caching capability >to TEZ to bring it on par with SPARK.
Nope, that was the crux of the earlier email. "Caching" seems to be catch-all term misused in that comparison. >> There is a big difference between where LLAP & SparkSQL, which has to do >> with access pattern needs. On another note, LLAP can actually be used inside Spark as well, just use LlapContext instead of HiveContext. <http://www.slideshare.net/HadoopSummit/llap-subsecond-analytical-queries-i n-hive/30> I even have a Postgres FDW for LLAP, which is mostly used for analytics web dashboards which are hooked into Hive. https://github.com/t3rmin4t0r/llap_fdw LLAP can do 200-400ms queries, but Postgres can get to the sub 10ms when it comes to slicing-dicing result sets <100k rows. Cheers, Gopal
