sohurdc opened a new issue, #7161:
URL: https://github.com/apache/kyuubi/issues/7161

   ### 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
   
   Kyuubi job status always shows as "Succeeded" even when the actual job has 
failed.
   My execution script is as follows:
   beeline -u 
"jdbc:hive2://kyuubiserver.my.com:10009/myuser;principal=hive/[email protected];hive.server2.proxy.user=myuser"
 --hiveconf spark.yarn.queue=center --hiveconf spark.executor.memory=4g  -e 
"insert overwrite directory 'hdfs:///user/myuser/tmp/2025-07-23' select * from 
..."
   
   then job faied with error such as:
   Caused by: org.apache.kyuubi.plugin.spark.authz.AccessControlException: 
Permission denied: user [myuser] does not have [write] privilege on ...
   
   But the final job status shown on the Spark log page is "Succeeded", which 
makes it impossible to determine the actual job outcome based on the job 
status. This hinders accurate job monitoring and retry mechanisms.
   
   <img width="647" height="413" alt="Image" 
src="https://github.com/user-attachments/assets/9ed3e200-d1e4-4499-b9a9-93e7ff220f71";
 />
   
   ### Affects Version(s)
   
   1.10.2
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Server Configurations
   
   ```yaml
   
   ```
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   
   ```
   
   ### 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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to