You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Xiangdong Huang (Jira)" <ji...@apache.org> on 2021/09/26 00:55:00 UTC

[jira] [Created] (IOTDB-1736) Error code is not printed in TSServiceImpl's log

Xiangdong Huang created IOTDB-1736:
--------------------------------------

             Summary: Error code is not printed in TSServiceImpl's log
                 Key: IOTDB-1736
                 URL: https://issues.apache.org/jira/browse/IOTDB-1736
             Project: Apache IoTDB
          Issue Type: Task
          Components: Core/Server
            Reporter: Xiangdong Huang
             Fix For: 0.13.0


In  TSServiceImpl.onNPEOrUnexpectedException(), the log does not print the errorcode:

For example:

 {code:java}
WARN  [2021-09-26 08:21:26,544] [pool-576-IoTDB-RPC-Client-2] org.apache.iotdb.db.service.TSServiceImpl:2211 - Status code: INTERNAL_SERVER_ERROR, MSG: UnSupported dataType: Unsupported data type in aggregation SUM : BOOLEAN 
WARN  [2021-09-26 08:21:26,546] [pool-576-IoTDB-RPC-Client-2] org.apache.iotdb.db.service.TSServiceImpl:2213 - Status code: INTERNAL_SERVER_ERROR, MSG: [INTERNAL_SERVER_ERROR] Exception occurred: "SELECT avg(status) FROM root.ln.wf01.wt01". executeStatement failed.  
{code}

To make it easy to check what error that users occur, both the error code (e.g., 500) and the error name (e.g., INTERNAL_SERVER_ERROR) should be printed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)