dengzhhu653 commented on PR #6427:
URL: https://github.com/apache/hive/pull/6427#issuecomment-4386027065

   > @dengzhhu653 @wecharyu Looks like, we have seen a long stacktrace every 
time `NoSuchObjectException` is thrown. In my opinion, this is typically too 
verbose and disk-consuming, and the log level is too high. Can we generate more 
moderate logs?
   > 
   > ```
   > 2026-05-06T04:22:34,429 ERROR [qtp1381730594-61] 
handler.AbstractRequestHandler: GetTableHandler 
[64b67b42-368e-42f3-82e9-b77a034ebaf7-3] Failed
   > java.util.concurrent.ExecutionException: 
NoSuchObjectException(message:hive.default.does_not_exist table not found)
   >    at 
com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:503)
   >    at 
com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:462)
   >    at 
com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:79)
   >    at 
org.apache.hadoop.hive.metastore.handler.AbstractRequestHandler.getRequestStatus(AbstractRequestHandler.java:227)
   >    at 
org.apache.hadoop.hive.metastore.handler.AbstractRequestHandler.getResult(AbstractRequestHandler.java:284)
   >    at 
org.apache.hadoop.hive.metastore.handler.GetTableHandler.getTable(GetTableHandler.java:609)
   >    at 
org.apache.hadoop.hive.metastore.HMSHandler.get_table_req(HMSHandler.java:1431)
   >    at 
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
   > ```
   
   make sense, does it log repeatedly? I assume such messages won't consume so 
much disk compared to older NoSuchObjectException


-- 
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