You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2020/02/26 13:49:00 UTC

[jira] [Closed] (IOTDB-520) Result of IBatchReader should not cross partition

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

Jialin Qiao closed IOTDB-520.
-----------------------------
    Fix Version/s:     (was: master branch)
                   0.10.0-SNAPSHOT
       Resolution: Fixed

> Result of IBatchReader should not cross partition
> -------------------------------------------------
>
>                 Key: IOTDB-520
>                 URL: https://issues.apache.org/jira/browse/IOTDB-520
>             Project: Apache IoTDB
>          Issue Type: Improvement
>            Reporter: Tian Jiang
>            Assignee: Zesong Sun
>            Priority: Major
>              Labels: batch, distributed, pull-request-available, query
>             Fix For: 0.10.0-SNAPSHOT
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Situation:
> Assuming daily partitioning.
> Node A manages the data of Day1,3,5 and Node B manages the data of Day2,4. In the current implementation, when the coordinator node fetches a batch from Node A, the batch may contain data of Day1,3 and the batch from Node B contains data of Day2. As a result, the coordinator node must merge the two batches to retain an ordered batch.
> But if the batches never cross the partition border, the coordinator node will be able to just return the batches without merging using a heap comparing the first element of each batch, which could reduce the merging overheads. 



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