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

   ### 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
   
   The Trino engine does not have a default schema. When results.getColumns is 
null, executing certain SQL statements, such as 'use database,' will throw an 
exception.
   
   ### Affects Version(s)
   
   master
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   24/01/12 17:31:17,003 [KyuubiTBinaryFrontendHandler-Pool: Thread-118] ERROR 
KyuubiTBinaryFrontendService: Error getting result set metadata: 
   org.apache.thrift.transport.TTransportException: null
        at 
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
 ~[libthrift-0.9.3.jar:0.9.3]
        at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.transport.TSaslTransport.readLength(TSaslTransport.java:376) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.transport.TSaslTransport.readFrame(TSaslTransport.java:453) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.transport.TSaslTransport.read(TSaslTransport.java:435) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.transport.TSaslClientTransport.read(TSaslClientTransport.java:37)
 ~[libthrift-0.9.3.jar:0.9.3]
        at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:429) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:318) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:219)
 ~[libthrift-0.9.3.jar:0.9.3]
        at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:77) 
~[libthrift-0.9.3.jar:0.9.3]
        at 
org.apache.hive.service.rpc.thrift.TCLIService$Client.recv_GetResultSetMetadata(TCLIService.java:544)
 ~[hive-service-rpc-3.1.3.jar:3.1.3]
        at 
org.apache.hive.service.rpc.thrift.TCLIService$Client.GetResultSetMetadata(TCLIService.java:531)
 ~[hive-service-rpc-3.1.3.jar:3.1.3]
        at 
org.apache.kyuubi.client.KyuubiSyncThriftClient.$anonfun$getResultSetMetadata$1(KyuubiSyncThriftClient.scala:393)
 ~[kyuubi-server_2.12-1.6.1-incubating.jar:1.6.1-incubating]
        at 
org.apache.kyuubi.client.KyuubiSyncThriftClient.$anonfun$withLockAcquiredAsyncRequest$2(KyuubiSyncThriftClient.scala:142)
 ~[kyuubi-server_2.12-1.6.1-incubating.jar:1.6.1-incubating]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
~[?:1.8.0_121]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 ~[?:1.8.0_121]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 ~[?:1.8.0_121]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
~[?:1.8.0_121]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
~[?:1.8.0_121]
        at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_121]
   ```
   
   
   ### 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?
   
   - [X] 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