In the high concurrency scenario, the query performance of spark SQL is limited 
by namenode and hive Metastore. There are some caches in the code, but the 
effect is limited. Do we have a practical and effective way to solve the 
time-consuming problem of driver in concurrent query?

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org

Reply via email to