[ 
https://issues.apache.org/jira/browse/IOTDB-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xuan Ronaldo reassigned IOTDB-1887:
-----------------------------------

    Assignee: Xuan Ronaldo

> In a clean IOTDB, without creating metadata, directly importing data 
> containing null indicates an exception
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: IOTDB-1887
>                 URL: https://issues.apache.org/jira/browse/IOTDB-1887
>             Project: Apache IoTDB
>          Issue Type: Bug
>          Components: Tools/Others
>    Affects Versions: 0.12.3
>            Reporter: xiaozhihong
>            Assignee: Xuan Ronaldo
>            Priority: Major
>
> The process is as follows:
> Step 1: start a clean Iotdb sever
> Step 2: Execute import command
> ./import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f 
> /home/xzh/csv-data/sg.txt
> Then will see log:
> 15:31:51.210 [main] DEBUG org.apache.iotdb.session.Session - 
> EndPoint(ip:127.0.0.1, port:6667) execute sql select * from 
> root.sg.d1,root.sg.d2 limit 1
> yyyy-MM-dd'T'HH:mm:ss.SSSX
> Line 3: null can't convert to INT32
> Line 3: null can't convert to FLOAT
> Line 4: null can't convert to INT32
> Line 4: null can't convert to FLOAT
> Line 1: null can't convert to INT64
> Line 1: null can't convert to INT64
> Line 1: null can't convert to INT64
> Line 2: null can't convert to INT64
> Line 2: null can't convert to INT64
> Line 2: null can't convert to INT64
> Line 3: 2.0 can't convert to INT64
> Line 3: null can't convert to INT64
> Line 4: 2.0 can't convert to INT64
> Line 4: true can't convert to INT64
> Import completely!
> sg.txt
> ```
> Time,root.sg.d1.s1,root.sg.d1.s2,root.sg.d2.s1,root.sg.d2.s2,root.sg.d2.s3
> 2020-08-18T10:22:31.603+08:00,1,2.0,null,null,null
> 2020-08-18T10:22:35.631+08:00,1,2.0,null,null,null
> 2020-08-18T10:22:41.093+08:00,null,null,1,2.0,null
> 2020-08-18T10:22:52.603+08:00,null,null,1,2.0,true
> ```
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to