Hi,
> So I believe it's better for `delete storage group FullPath` command to
> support wildcard, which can be regarded as `delete storage group `
+1, this is a good function
Thanks,
--
Jialin Qiao
School of Software, Tsinghua University
乔嘉林
清华大学 软件学院
> -原始邮件-
> 发件人: "谭新宇"
> 发送时间:
Hi all,
great discussion ... I guess the first bug reports you got from me when working
on the initial maven build were related to this :-)
By the way ... why not use the default Timezone configured for the VM running
the client code?
I don't even think there is a need to manually configure
Hi,
very good addition, indeed.
As one of the first users "far away" from China it was always a bit of math for
me to get everything together with default settings (UTC+8?) : )
Julian
Am 30.10.20, 02:59 schrieb "Xiangwei Wei" :
In the previous design, the timezone was set in IoTDB server
Greetings,
Currently IoTDB Session API only support to insert data using synchronous
interfaces, such as insertRecord(), insertTablet(), etc. Using synchronous
interfaces, client thread has to wait until the insertion finishes.
We are about to support asynchronous session API in future 0.11
Hi Rongzhao,
Good job, I think you can fix the bug that Yanhong created on the issue[1]
together with this PR, it may need to change the code in Cli module.
Besides the commit id before[2] can run correctly, so this may be newly
introduced.
[1] https://issues.apache.org/jira/browse/IOTDB-973
Hi all,
Good job! But there is still some problems using command line executing
start-cli.sh -e
ie. start-cli.sh -e 'show storage group'
I submitted this bug in jira, please check:
https://issues.apache.org/jira/browse/IOTDB-973
Thank you,
Yanhong Wang
Hi,
I've submitted a PR for issue IOTDB-972
[https://github.com/apache/iotdb/pull/1906]. I used code that .sh couldn't
recognize. Now I change the start-cli.sh file into sh version
Thanks,
---
Rongzhao Chen
School of Software, Tsinghua University
Greetings,
Currently, it seems that the user can delete all data and timeseries:
delete timeseries root.*;
But this sql cann't delete all related storage groups. In addition, such an
approach would be more time-consuming than simply deleting specified storage
groups.
So I believe it's
