[jira] [Commented] (IOTDB-763) Add Test for the "Client-py" module and trigger the test in Travis

["Xiangdong Huang (Jira)" <ji...@apache.org>]

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

Xiangdong Huang commented on IOTDB-763:
---------------------------------------

By the way, we'd better to wrap current raw API to make it easier to let users use it.

For example, I find some codes in client_example.py:

 
{code:java}
// code placeholder
# the first 3 belong to 's1', the second 3 belong to 's2'... the last 3
# belong to 's6'
# to transfer a string, you must first send its length and then its bytes
# (like the last 3 'i7s'). Text values should start and end with ' or ".
# IoTDB use big endian in rpc
value_pack_str = '>3q3i3d3f3bi7si7si7s'
time_pack_str = '>3q'
encoding = 'utf-8'
{code}
It is.... antihuman coding...

 

 

> Add Test for the "Client-py" module and trigger the test in Travis
> ------------------------------------------------------------------
>
>                 Key: IOTDB-763
>                 URL: https://issues.apache.org/jira/browse/IOTDB-763
>             Project: Apache IoTDB
>          Issue Type: Task
>          Components: Client/Python
>            Reporter: Xiangdong Huang
>            Priority: Major
>
> Currently, we generate the python lib in service-rpc module (under the service-rcp/target/generated-sources-python). 
> We also have a module "client-py", which provides an example for telling user how to use IoTDB in python.
>  
> However, as there is no test mechanisms, we are hard to guarantee whether the client-py follows the latest rpc interface.
>  



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