[
https://issues.apache.org/jira/browse/IOTDB-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028668#comment-17028668
]
Xiangdong Huang commented on IOTDB-446:
---------------------------------------
yes I can,
see the following case:
IoTDB> create timeseries root.sg1.d1.1_2 with datatype=float,encoding=rle;
create timeseries root.sg1.d1.1_2 with datatype=float,encoding=rle;
Msg: line 1:31 mismatched input '_' expecting \{WITH, '.'}
It costs 0.178s
> Can not create or query time series whose path starts with a digit but has
> strings
> ----------------------------------------------------------------------------------
>
> Key: IOTDB-446
> URL: https://issues.apache.org/jira/browse/IOTDB-446
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Planner/SQLParser
> Affects Versions: 0.9.1
> Reporter: Xiangdong Huang
> Priority: Major
>
> Hi,
> can we support a path starting with number but actually being a string?
> like:
> create timeseries root.a.b.d_1.1s with datatype=FLOAT,encoding=RLE;
>
> It is common because if there is float number in the path, then users may
> replace the "." with "_",
> e.g., the temperature of a station with id 535 on longitude 120.3455, then
> we can define a path like: root.535.120_3455.temperature.
>
> In version 0.9.1, the above time series can not be created successfully if we
> use "create timeseries" statement, but if we allow creating time series
> automatically, the above time series can be created successfully (because we
> just do not support it in the SQLParser module).
> But, when we want to query on such a time series, SQL parser error will occur.
>
> see:
> 1. create failed case:
>
> {code:java}
> // code placeholder
> IoTDB> create timeseries root.a.b.d_1.1s with datatype=FLOAT,encoding=RLE;
> Msg: Statement format is not right: Parsing error, statement [create
> timeseries root.a.b.d_1.1s with datatype=FLOAT,encoding=RLE] failed when
> parsing AST tree to generate logical operator. Detailed information: [line
> 1:31 mismatched input '1s' expecting set null]
> {code}
> 2. create successfully by auto-creating.
>
>
> {code:java}
> // code placeholder
> IoTDB> show child paths root.national.4.5.585.9_6666.9_333.88_9;
> +-------------------------------------------------------------------+
> | Child Paths|
> +-------------------------------------------------------------------+
> | root.national.4.5.585.9_6666.9_333.88_9.minimumTemperature24HQC|
> | root.national.4.5.585.9_6666.9_333.88_9.windSpeed2minQC|
> | root.national.4.5.585.9_6666.9_333.88_9.dewPoint|
> | root.national.4.5.585.9_6666.9_333.88_9.precipitation1HQC|
> | root.national.4.5.585.9_6666.9_333.88_9.surfaceTemperatureQC|{code}
>
> 3. query failed:
>
> {code:java}
> // code placeholder
> IoTDB> select windDirection10min from root.national.4.5.585.9_6666.9_333.88_9;
> Msg: Statement format is not right: Parsing error, statement [select
> windDirection10min from root.national.4.5.585.9_6666.9_333.88_9] failed when
> parsing AST tree to generate logical operator. Detailed information: [line
> 1:58 missing EOF at '_6666' near '9'. Please refer to SQL document and check
> if there is any keyword conflict.]
> It costs 0.003s
> {code}
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
