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 2020/01/03 07:27:00 UTC

[jira] [Commented] (IOTDB-138) Refactor metadata RPC for serving JDBC

    [ https://issues.apache.org/jira/browse/IOTDB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007268#comment-17007268 ] 

Jialin Qiao commented on IOTDB-138:
-----------------------------------

[https://github.com/apache/incubator-iotdb/pull/697]

> Refactor metadata RPC for serving JDBC
> --------------------------------------
>
>                 Key: IOTDB-138
>                 URL: https://issues.apache.org/jira/browse/IOTDB-138
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: xiangdong Huang
>            Priority: Major
>              Labels: medium
>
> Hi, current the fetchMetadata() function in TsServiceImpl is a little ugly and inefficient.
> It is better to rethink the function.
> Before doing that, we need to discuss what the concepts of "database", "catalog", "schema", "table" and "column" meas in IoTDB.
>  
>  



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