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

Posted to reviews@iotdb.apache.org by GitBox <gi...@apache.org> on 2021/02/02 02:27:40 UTC

[GitHub] [iotdb] yuqi1129 commented on pull request #902: [IOTDB-28] Calcite Integration for IoTDB

yuqi1129 commented on pull request #902:
URL: https://github.com/apache/iotdb/pull/902#issuecomment-771303075


   @wangchao316 , Hi, about your problem, we may do the following as far as i known
   1. Skip the optimization stage, that is, we only use the parser to convert sql to ast then validate and transfer the ast to logical RelNode, avatica builtin logical indeed is heavy for simple query, especially for time scales sql, this may need to change the calcite source code and maintain our own version if we want to solve this.
   2. this problem seems the problem the SQL itself , we do not recommend too many values in in clause,  due to the limit about the field in java language, we can't solve it well.
   
   The above is a personal point of view, discussion is wanted  


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org