Hi,
It can be a feature but I can’t see much of the meaning in it. Using automatic schema creation would be better in most cases. And it is absolutely not a bug, we never said wildcard is allowed in such statements, anyone who has that thought should read our manual again. Tian Jiang | | Tian Jiang | | [email protected] | 签名由网易邮箱大师定制 On 12/20/2019 13:03，Xiangdong Huang<[email protected]> wrote： Hi, I leave a detail comment on jira. Sounds `set storage group to root.ed.* ` is also meaningful (which means set the third level of the schema as storage groups), Do we support that now? If not, it should be considered a bug now.. Best. ---------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 chenzhengwei (Jira) <[email protected]> 于2019年12月20日周五 上午11:22写道： chenzhengwei created IOTDB-380: ---------------------------------- Summary: Questions about asterisks in storage group or time series paths Key: IOTDB-380 URL: https://issues.apache.org/jira/browse/IOTDB-380 Project: Apache IoTDB Issue Type: Bug Reporter: chenzhengwei version : 0.9.0 System : windows scenario one: 1, set storage group to root.ed do success 2, create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE 3, exception : Msg: Statement format is not right: Parsing error, statement [create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE] failed when parsing AST tree to generate logical operator. Detailed information: [line 1:32 mismatched input '*' expecting set null] scenario two: 1, set storage group to root.ed.* or set storage group to root.ed.*.xx do success 2, create timeseries root.ed.fc02.abc with datatype=INT32,encoding=RLE or create timeseries root.ed.fc02.xx with datatype=INT32,encoding=RLE 3, exception: Msg: The seriesPath of [root.ed] already exist, it can't be set to the storage group * Now I don't know how to use the * in the path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
