[jira] [Commented] (IOTDB-1539) The delete operation is incorrect
[
https://issues.apache.org/jira/browse/IOTDB-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396475#comment-17396475
]
Haonan Hou commented on IOTDB-1539:
---
Hi, the deletion of IoTDB doesn't support value filter yet.
For now, I think we should disable this deletion statement until this feature
is implemented.
> The delete operation is incorrect
> -
>
> Key: IOTDB-1539
> URL: https://issues.apache.org/jira/browse/IOTDB-1539
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Server
>Affects Versions: 0.12.2-SNAPSHOT
>Reporter: 刘珍
>Priority: Critical
> Attachments: image-2021-07-30-16-39-20-761.png,
> image-2021-08-06-16-50-55-695.png, image-2021-08-06-16-59-04-947.png,
> image-2021-08-06-17-04-11-376.png
>
>
> iotdb
> rel/0.12 0728 88bc4289a61950cdb89c823b434931b280b98433
> cli :
> CREATE TIMESERIES root.sg1.dev1.s_1 WITH DATATYPE=INT32, ENCODING=PLAIN;
> CREATE TIMESERIES root.sg1.dev1.s_2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN;
> insert into root.sg1.dev1(time,s_1,s_2 ) values(1,99,0);
> insert into root.sg1.dev1(time,s_1,s_2 ) values(2,199,0);
> insert into root.sg1.dev1(time,s_1,s_2 ) values(3,299,1000);
> insert into root.sg1.dev1(time,s_1,s_2 ) values(4,399,1000);
> insert into root.sg1.dev1(time,s_1,s_2 ) values(5,499,0);
>
> flush;
> delete from root.sg1.dev1 where s_2>0;
> {color:#DE350B}*-- All data is deleted*{color}
> -- Suggestion ： give an error or perform correctly
> !image-2021-07-30-16-39-20-761.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1558) rel/0.12 : [Sync] During sync, the sender stops the Sync service and starts it again. The receiver resync some tsfiles
刘珍 created IOTDB-1558: - Summary: rel/0.12 : [Sync] During sync, the sender stops the Sync service and starts it again. The receiver resync some tsfiles Key: IOTDB-1558 URL: https://issues.apache.org/jira/browse/IOTDB-1558 Project: Apache IoTDB Issue Type: Bug Components: Sync Affects Versions: 0.12.2-SNAPSHOT Reporter: 刘珍 Attachments: config.properties, image-2021-08-10-14-11-47-458.png, image-2021-08-10-14-16-26-985.png, image-2021-08-10-14-20-03-960.png IoTDB ： rel/0.12 0809 75077fbfa62307e9cc0acdcd213d7b3c66f8ff27 1. benchmark generates data for sync config.properties The sender's data ： !image-2021-08-10-14-11-47-458.png! 2. Start the receiver service a. conf/iotdb-engine.properties : is_sync_enable=true b. Start the receiver service ./sbin/start-server.sh 3. Start the sender sync service 4. Stop the sender server About 40 gb of data is synchronized. Sender : ./sbin/stop-server.sh and the SyncClient service was also stopped Restart the SyncClient service : ../tools/start-sync-client.sh 5. The receiver log_error.log : !image-2021-08-10-14-16-26-985.png! !image-2021-08-10-14-20-03-960.png! 1628570916564-4131-0-0.tsfile is synchronized twice on the receiver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1557) rel/0.12 : [Sync] mlog.bin sync failed
刘珍 created IOTDB-1557:
-
Summary: rel/0.12 : [Sync] mlog.bin sync failed
Key: IOTDB-1557
URL: https://issues.apache.org/jira/browse/IOTDB-1557
Project: Apache IoTDB
Issue Type: Bug
Components: Sync
Affects Versions: 0.12.2-SNAPSHOT
Reporter: 刘珍
Attachments: config.properties, image-2021-08-10-11-22-00-216.png
IoTDB :
rel/0.12 0809 75077fbfa62307e9cc0acdcd213d7b3c66f8ff27
sender & receiver conf/iotdb-env.sh :
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE=4G
1. benchmark generates data for sync
benchmark configuration file : See the attachment .
2. Start the receiver service
a. conf/iotdb-engine.properties
is_sync_enable=true
b. Start the receiver service
3. Start the sender sync service
a. conf/iotdb-sync-client.properties
server_ip=x.x.x.x
sync_period_in_second=60
b. ./tools/start-sync-client.sh
4. sender : log_sync.log
!image-2021-08-10-11-22-00-216.png|thumbnail!
2021-08-10 09:39:01,856 [pool-1-IoTDB-sync-client-timer-1] ERROR
o.a.i.d.s.s.t.SyncClient:433 - {color:#DE350B}Digest check of schema file
{color}/home/iotdb/liuzhen_test/rel_12/db_0806/data/system/schema/{color:#DE350B}mlog.bin
failed{color}, retry
2021-08-10 09:39:01,863 [pool-1-IoTDB-sync-client-timer-1] ERROR
o.a.i.d.s.s.t.SyncClient:224 - Sync failed
org.apache.iotdb.db.exception.SyncConnectionException: Can not sync schema
after 5 retries.
at
org.apache.iotdb.db.sync.sender.transfer.SyncClient.syncSchema(SyncClient.java:380)
at
org.apache.iotdb.db.sync.sender.transfer.SyncClient.syncAll(SyncClient.java:247)
at
org.apache.iotdb.db.sync.sender.transfer.SyncClient.lambda$startTimedTask$2(SyncClient.java:222)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IOTDB-1552) Filter s1 > 1 could be applied on a TEXT timeseries
[ https://issues.apache.org/jira/browse/IOTDB-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jihang reassigned IOTDB-1552: - Assignee: jihang > Filter s1 > 1 could be applied on a TEXT timeseries > --- > > Key: IOTDB-1552 > URL: https://issues.apache.org/jira/browse/IOTDB-1552 > Project: Apache IoTDB > Issue Type: Bug > Components: Query >Affects Versions: 0.12.1 >Reporter: Jialin Qiao >Assignee: jihang >Priority: Major > Attachments: image-2021-08-05-15-20-18-536.png > > > create timeseries root.turbine1.d1.s1 with datatype=TEXT, encoding=PLAIN, > compression=SNAPPY > insert into root.turbine1.d1(timestamp,s1) values(1,1.1); > !image-2021-08-05-15-20-18-536.png|width=423,height=226! > s1>1 should throw exception for a TEXT timeseries > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1556) Empty device node without storage group after auto create tiemseries failure
Yukun Zhou created IOTDB-1556: - Summary: Empty device node without storage group after auto create tiemseries failure Key: IOTDB-1556 URL: https://issues.apache.org/jira/browse/IOTDB-1556 Project: Apache IoTDB Issue Type: Bug Components: Server Reporter: Yukun Zhou Fix For: master branch, 0.12.2-SNAPSHOT -- This message was sent by Atlassian Jira (v8.3.4#803005)
