Hi Julian,
Thanks!
Actually, I occur some problems when release iotdb-py-client 0.11.0 to pypi.
After checking your modifications and under the help of Kaifeng Xue,
I think I fixed them. see PR[1] and [2].
(I uniform the package name as `iotdb`)
[1] https://github.com/apache/iotdb/pull/2127
[2]
By the way, tests are not contained in the PR.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Xiangdong Huang 于2020年11月26日周四 下午6:07写道：
> Hi Julian,
>
> Thanks!
> Actually, I occur some problems when release iotdb-py-client 0.11
Hi Xiangdong,
thanks for your work.
Indeed your module looks good now (init.py everywhere and such things).
I will also add the Support for python-testcontainers in the official code as
ist quite neat for tests.
Julian
Am 26.11.20, 11:09 schrieb "Xiangdong Huang" :
By the way, tests are
If a query takes too much time, we'd better interrupt this query instead of
hanging up the client.
The design doc is in [1]. Any advice is appreciated :D
A discussion is:
How long can the query be considered as time out? maybe 5min, 10min? We
need to set a default value, of course it can be modif
Hi,
I'm a little skeptical about the motivation for this feature.
If a large query really needs to take a long time to execute, is throwing an
exception on the client side graceful?
For example, in some test scenarios, I would usually write hundreds of millions
of points of data, and then p
Sorry, as this parameter is configurable, it seems my problem can be solved ~
Then I have no problem with this feature and design~
Best
———
Xinyu Tan
> 在 2020年11月26日，下午9:32，Xiangwei Wei 写道：
>
> If a query takes too much time, we'd better interrupt this query instead of
> hanging up the client.
Greetings,
This is important indeed, but I have some suggestions:
1. This would best be based query cancellation, i.e., a query can be cancelled
by a given interface, and the timed thread need only to call this interface to
time out a query when needed. The merit of doing so is better abstracti
Hi,
+1 for Tian Jiang ideas,
And I think we can extend the session api to add one parameter to indicate the
operation timeouts(insert、query and so on), besides we can implement the
`setQueryTimeout()` method in JDBC.
Thanks,
---
Houliang Qi
BONC, Ltd
On 11
The Apache IoTDB team is pleased to announce the release of Apache IoTDB
0.11.0.
Apache IoTDB (Database for Internet of Things) is an IoT native database
with high performance for data management and analysis, deployable on the
edge and the cloud.
This is the first release version after Apache Io
Hi,
Great work! Thanks Xiangdong!
--
Jialin Qiao
School of Software, Tsinghua University
乔嘉林
清华大学 软件学院
> -原始邮件-
> 发件人: "Xiangdong Huang"
> 发送时间: 2020-11-27 12:17:05 (星期五)
> 收件人: [email protected]
> 抄送: [email protected], dev
> 主题: [ANNOUNCE] Apache IoTDB 0.11.0 released
>
>
Hi,
+1 for setting timeout in query and abstracting the cancel interface
Thanks,
--
Jialin Qiao
School of Software, Tsinghua University
乔嘉林
清华大学 软件学院
> -原始邮件-
> 发件人: "Houliang Qi"
> 发送时间: 2020-11-27 10:23:24 (星期五)
> 收件人: "[email protected]"
> 抄送:
> 主题: Re: The design doc of [IOTDB
Hi all,
Thanks for your response~
> Query time out should be defined at query level, or at least session
level.
Big +1 for that. We can provide a new method to set timeout by JDBC and
session. And provide one local timeout parameter when executing query
statement.
> This would best be based qu
12 matches
Mail list logo
