[Bug] DBeaver is slow to obtain and display data

[SGITLOGIN]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues and found no similar issues.

Describe the bug

The default query of dbeaver displays 200 rows. Each pull-down will display 200 more rows of data. There is a table with a total of 990 data.

1. Every time I pull down to display more data, it will generate new SQL to query. Is this as expected? Is it possible to get the results of the previous query?
2. Each time you pull down to display more data, the time it takes to return and display the data will increase a lot.

Affects Version(s)

1.10.0

Kyuubi Server Log Output

No response

Kyuubi Engine Log Output

No response

Kyuubi Server Configurations

No response

Kyuubi Engine Configurations

spark.master yarn
spark.yarn.queue default
spark.executor.cores 1
spark.driver.memory 3g
spark.executor.memory 3g
spark.dynamicAllocation.enabled true
spark.dynamicAllocation.shuffleTracking.enabled true
spark.dynamicAllocation.minExecutors 1
spark.dynamicAllocation.maxExecutors 10
spark.dynamicAllocation.initialExecutors 1
spark.cleaner.periodicGC.interval 5min

Additional context

No response

Are you willing to submit PR?

• Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
• No. I cannot submit a PR at this time.

[pan3793]

Summarize the conclusions of the offline discussion: kyuubi-beeline takes 3s to run the same query, including retrieving and displaying the result to console, which indicates the performance bottleneck comes from the DBeaver side.

[pan3793]

A user from the Kyuubi community catches this performance regression caused by #6639, the Kyuubi developers are working on fixing it(patch will be included in 1.10.1, the release is scheduled in a month), and to work around it you can downgrade the Kyuubi JDBC driver to 1.9.2 for now.