You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "张洪胤 (Jira)" <ji...@apache.org> on 2021/09/29 01:07:00 UTC
[jira] [Reopened] (IOTDB-1645) benchmark correctness check
[ https://issues.apache.org/jira/browse/IOTDB-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
张洪胤 reopened IOTDB-1645:
------------------------
> benchmark correctness check
> ---------------------------
>
> Key: IOTDB-1645
> URL: https://issues.apache.org/jira/browse/IOTDB-1645
> Project: Apache IoTDB
> Issue Type: New Feature
> Reporter: Hai Liu
> Assignee: 张洪胤
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In this Problem, I optimize the logic of query generate and support point verification between two database. The details are as follows.
> # I modify the timestamp generate logic of Q1-Q10: timestamp increment for each operation separately.
> # I support point verification between two database: compare between each other, use IS_POINT_COMPARISON to use this function.
> # Add check of config: IS_COMPARISON and IS_POINT_COMPARISON only used in double write mode and can't be both true
> # And fix not aligned sensor for timescaleDB
--
This message was sent by Atlassian Jira
(v8.3.4#803005)