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

Posted to dev@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2019/12/03 03:25:00 UTC

[jira] [Created] (IOTDB-334) Move limit&slimit parser to Server side

Jialin Qiao created IOTDB-334:
---------------------------------

             Summary: Move limit&slimit parser to Server side
                 Key: IOTDB-334
                 URL: https://issues.apache.org/jira/browse/IOTDB-334
             Project: Apache IoTDB
          Issue Type: Improvement
            Reporter: Jialin Qiao


In our query process, SQL will be analyzed by Antlr in the server-side, then generated to a logical plan. 

However, query SQL is also parsed in the client (IoTDBQueryResultSet) by the following statement to get the value of slimit and limit.

String[] splited = sql.toUpperCase().split("\\s+");

This causes extra parsing for a query, which will slow down the query speed.

I recommend moving the limit&slimit parsing to the server-side.



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