You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Xinyu Tan (Jira)" <ji...@apache.org> on 2022/01/26 03:33:00 UTC

[jira] [Created] (IOTDB-2494) Decouple user interfaces from thrift interfaces

Xinyu Tan created IOTDB-2494:
--------------------------------

             Summary: Decouple user interfaces from thrift interfaces
                 Key: IOTDB-2494
                 URL: https://issues.apache.org/jira/browse/IOTDB-2494
             Project: Apache IoTDB
          Issue Type: Improvement
            Reporter: Xinyu Tan


Currently, we define too many interfaces in thrift. As a result, every time we add a user interface, we need to add an RPC interface, which causes inconvenience in maintenance. In fact, we can abstract out several separate read-write RPC interfaces at the Thrift layer and then identify different requests through fields in the RPC structure rather than through different RPC interfaces. This reduces the maintenance burden of the new interface.

Before the abstract:
Add a new user interface -> Add a thrift interface -> Maintain a new user interface for all clients (call a new RPC function using a new RPC structure)

After the abstract:
Add a new user interface -> All clients maintain the new user interface (still using the old RPC structure to call the old RPC function, just update a new request id)

Job Description:
 * Correctness assurance and performance testing of all interfaces before and after abstraction
 * In order to ensure compatibility, it can be implemented by adding interfaces. This is compatible with older clients.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)