You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Haonan Hou (Jira)" <ji...@apache.org> on 2022/02/17 11:07:00 UTC

[jira] [Commented] (IOTDB-2548) When according to yyyy.MM.dd HH:mm:ss to write data, an error is reported.

    [ https://issues.apache.org/jira/browse/IOTDB-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493873#comment-17493873 ] 

Haonan Hou commented on IOTDB-2548:
-----------------------------------

The pr 5071 supported the usage of `2022.02.10`.

> When according to yyyy.MM.dd HH:mm:ss to write data, an error is reported.
> --------------------------------------------------------------------------
>
>                 Key: IOTDB-2548
>                 URL: https://issues.apache.org/jira/browse/IOTDB-2548
>             Project: Apache IoTDB
>          Issue Type: Bug
>          Components: Client/CLI, Core/Server
>    Affects Versions: 0.13.0-SNAPSHOT
>            Reporter: xiaozhihong
>            Assignee: Minghui Liu
>            Priority: Minor
>              Labels: pull-request-available
>
>  
> In the CLI, according to the supported time format mentioned in the userguide to insert data , an error will be reported when yyyy.MM.dd HH:mm:ss is encountered.
> {code:java}
> IoTDB> insert into root.ln.wf01.wt01(time,temperature) values(2022.02.10 10:12:10,12.12)
> Msg: 401: Error occurred while parsing SQL to physical plan: line 1:66 extraneous input '10:12:10' expecting {NOW, '-', '+', '.', ',', '(', ')', STRING_LITERAL, DATETIME_LITERAL, INTEGER_LITERAL, EXPONENT_NUM_PART, BOOLEAN_LITERAL, NULL_LITERAL, NAN_LITERAL} {code}
> If the time format of yyyy.MM.dd HH:mm:ss is not supported in V0.13, this part of the content needs to be removed in the userguide.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)