You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "FengQingxin (Jira)" <ji...@apache.org> on 2022/04/21 09:47:00 UTC
[jira] [Commented] (IOTDB-1669) Incorrect error code returned when SQLParserException happened
[ https://issues.apache.org/jira/browse/IOTDB-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525596#comment-17525596 ]
FengQingxin commented on IOTDB-1669:
------------------------------------
!image-2022-04-21-17-46-42-225.png!
> Incorrect error code returned when SQLParserException happened
> --------------------------------------------------------------
>
> Key: IOTDB-1669
> URL: https://issues.apache.org/jira/browse/IOTDB-1669
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
> Reporter: Zhong Wang
> Assignee: Zhong Wang
> Priority: Major
> Attachments: image-2022-04-21-17-46-42-225.png
>
>
> Currently, the error code returned when an SQLParserException happened is 301, which represents a METADATA_ERROR.
>
> For example, for the following query
>
> {code:java}
> select * from root.sg.* limit 2147483648{code}
>
>
> The error message will be like
> {code:java}
> Msg: 303: Check metadata error: Out of range. LIMIT <N>: N should be Int32.
> {code}
> which is quite confusing because it has nothing to do with the metadata and the cause of the error is simply an integer overflow.
>
> I will fix this issue.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)