Github user shaolinliu commented on the issue:
https://github.com/apache/spark/pull/17581
My opinion is:
In the production, the user often select without a limit, often lead to
service offline,this is a general situation, so increase the parameters.
When SQLConf.THRIFTSERVER_INCREMENTAL_COLLECT is open, the process is :
beeline[get] -> hs2[get] -> executor[ret] -> hs2[ret] ->beeline[ret] ....
and in the process,the executor's resource is occupied, and when it it
close,the process is:
beeline[get] -> hs2[collect] -> beeline[ret].
similar to the redis's pipeline to enhance performance, and reducing the
time will reduce resources too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
