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/02/02 10:48:00 UTC

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

     [ https://issues.apache.org/jira/browse/IOTDB-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jialin Qiao closed IOTDB-138.
-----------------------------
    Fix Version/s: 0.10.0-SNAPSHOT
       Resolution: Fixed

> 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
>            Assignee: Boris Zhu
>            Priority: Major
>              Labels: medium, pull-request-available
>             Fix For: 0.10.0-SNAPSHOT
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)