Comparing to restful API, using javascript API reduces JSON parse and can
use all session functions. If we do this, I think we should publish a
javascript/typescript connector package in npm (like a maven in java). By
the way, I develop a simple grafanan iotdb plugin (
https://github.com/Genius-pig/iotdb) by using rest API (
https://github.com/apache/iotdb/pull/1716). restApi is more common, it
transfers data through HTTP, so you can use it in any client in any
language.

On Tue, Nov 10, 2020 at 2:35 PM Jialin Qiao <[email protected]>
wrote:

> Hi,
>
> Thank you for sharing the use case! Currently we do not have a JavaScript
> API.
>
> However, since we use thrift [1] as the RPC framework, you could generate
> the JavaScript API easily.
>
> Please refer to the usage of Python API [2]
>
> [1] https://github.com/apache/iotdb/tree/master/thrift
> [2] https://github.com/apache/iotdb/tree/master/client-py
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> &gt; -----原始邮件-----
> &gt; 发件人: "Shi Jinghai" <[email protected]>
> &gt; 发送时间: 2020-11-09 13:29:42 (星期一)
> &gt; 收件人: "[email protected]" <[email protected]>
> &gt; 抄送:
> &gt; 主题: Re: Embdedded IoTDB Grafana Endpoint
> &gt;
> &gt; As I’m working on an edge system design, I’d suggest running IoTDB in
> Node-RED environment and use Grafana in Node-RED.
> &gt;
> &gt; BTW, is there any Javascript connector ready for IoTDB?
> &gt;
> &gt; Shi Jinghai
> &gt;
> &gt;
> &gt; 发件人: Jialin Qiao<mailto:[email protected]>
> &gt; 发送时间: 2020年11月7日 12:22
> &gt; 收件人: [email protected]<mailto:[email protected]>
> &gt; 主题: Re: Embdedded IoTDB Grafana Endpoint
> &gt;
> &gt; Hi,
> &gt;
> &gt; &gt; I dislike the idea of having spring in the server as well.
> &gt;
> &gt; +1, could we combine the small handler with our RestAPI?
> &gt;
> &gt; Thanks,
> &gt; --
> &gt; Jialin Qiao
> &gt; School of Software, Tsinghua University
> &gt;
> &gt; 乔嘉林
> &gt; 清华大学 软件学院
> &gt;
> &gt; &gt; -----原始邮件-----
> &gt; &gt; 发件人: "Julian Feinauer" <[email protected]>
> &gt; &gt; 发送时间: 2020-11-06 22:38:50 (星期五)
> &gt; &gt; 收件人: "[email protected]" <[email protected]>
> &gt; &gt; 抄送:
> &gt; &gt; 主题: Re: Embdedded IoTDB Grafana Endpoint
> &gt; &gt;
> &gt; &gt; Hey,
> &gt; &gt;
> &gt; &gt; yes, to do it clean we could do it directly without Spring. Then
> ist just a very small handler.
> &gt; &gt; Similar to what we already use optionally in the prometheus
> module.
> &gt; &gt;
> &gt; &gt; I dislike the idea of having spring in the server as well.
> &gt; &gt;
> &gt; &gt; Julian
> &gt; &gt;
> &gt; &gt; Am 06.11.20, 12:03 schrieb "Xiangdong Huang" <
> [email protected]>:
> &gt; &gt;
> &gt; &gt;     Hi,
> &gt; &gt;
> &gt; &gt;     &gt; what do you think of an option to run the SimpleJson
> Grafana Connector
> &gt; &gt;     directly in IoTDBs Server Context (could be disbaled by
> default).
> &gt; &gt;     it is ok.
> &gt; &gt;
> &gt; &gt;     But I think we need to prune some dependencies of Spring...
> It it too large
> &gt; &gt;     now.. (I remember it is ~ 20MB to add such a module)
> &gt; &gt;
> &gt; &gt;     Best,
> &gt; &gt;     -----------------------------------
> &gt; &gt;     Xiangdong Huang
> &gt; &gt;     School of Software, Tsinghua University
> &gt; &gt;
> &gt; &gt;      黄向东
> &gt; &gt;     清华大学 软件学院
> &gt; &gt;
> &gt; &gt;
> &gt; &gt;     Julian Feinauer <[email protected]>
> 于2020年11月6日周五 下午6:13写道:
> &gt; &gt;
> &gt; &gt;     &gt; Hi folks,
> &gt; &gt;     &gt;
> &gt; &gt;     &gt; as we just discussed the prometheus integration, what
> do you think of an
> &gt; &gt;     &gt; option to run the SimpleJson Grafana Connector directly
> in IoTDBs Server
> &gt; &gt;     &gt; Context (could be disbaled by default).
> &gt; &gt;     &gt; This would make it way easier for users to just „look“
> aat their IoTDB
> &gt; &gt;     &gt; Data.
> &gt; &gt;     &gt;
> &gt; &gt;     &gt; WDYT?
> &gt; &gt;     &gt;
> &gt; &gt;     &gt; Julian
> &gt; &gt;     &gt;
> &gt; &gt;
> &gt; </[email protected]></[email protected]></
> [email protected]></[email protected]>
> &gt;
> </mailto:[email protected]></mailto:[email protected]></
> [email protected]></[email protected]>

Reply via email to