apache / apache/kyuubi

[Bug] When HUE connects to KYUUBI, I am unable to stably run a large SQL task

Open
#4,927 2 comments 0 reactions 0 assignees View on GitHub
kind:bug priority:major
Dominant language
Scala
Stars
2.4k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

Question1:
I found that when I use HUE to query KYUUBI, if I can't get the result in 60 seconds. My query will fail. And I get the message "Result expired".
But when I use HUE to query HIVE, I can complete a large query normally.
What configuration items should I adjust in KYUUBI or HUE?

Question2:
When I run Kyubi SQL in batch on the HUE console, HUE often stops executing after the first few SQL runs.
When I run HIVE SQL with HUE, this does not happen.

### Affects Version(s)

KYUUBI:1.7.1 SPARK:3.3.2 HUE:4.10.0

### Kyuubi Server Log Output

_No response_

### Kyuubi Engine Log Output

_No response_

### Kyuubi Server Configurations

_No response_

### Kyuubi Engine Configurations

_No response_

### 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.
- [X] No. I cannot submit a PR at this time.

Contributor guide

Open the contributing guide

Research direction

No source file, test, server log, engine log, or configuration is provided. Start by reproducing the HUE-to-Kyuubi large-query and batch-SQL behavior with the listed versions, then inspect the server and engine configurations and logs; done means identifying the relevant timeout or execution failure and documenting or validating a fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
spark, sql
Domain
backend, data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.