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/11/21 05:45:00 UTC
[jira] [Commented] (IOTDB-4996) Fix insert null records bug when the data inside one SeriesPartitionSlot is divided into different TimePartitionSlot
[ https://issues.apache.org/jira/browse/IOTDB-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636452#comment-17636452 ]
Haonan Hou commented on IOTDB-4996:
-----------------------------------
https://github.com/apache/iotdb/pull/7944/commits/ffa09c6edd6e47fb61b8236d0d9edf86d9d9f645
> Fix insert null records bug when the data inside one SeriesPartitionSlot is divided into different TimePartitionSlot
> --------------------------------------------------------------------------------------------------------------------
>
> Key: IOTDB-4996
> URL: https://issues.apache.org/jira/browse/IOTDB-4996
> Project: Apache IoTDB
> Issue Type: Bug
> Reporter: Yongzao Dan
> Assignee: Haonan Hou
> Priority: Major
> Fix For: 0.14.0
>
>
> We've designed the StorageGroup fast activation function in IOTDB-4881. Therefore the data inside one SeriesPartitionSlot but with different TimePartitionSlots will easier to be allocated into different DataRegionGroup.
>
> And in [this|https://github.com/apache/iotdb/pull/7944] corresponding PR, the session insert null records test is failed. The possible reason is that the insert null records function is not adapted for aforesaid scenario.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)