[jira] [Created] (IOTDB-181) Remove "first_value" and "last_value" in TsDigest
Jialin Qiao created IOTDB-181: - Summary: Remove "first_value" and "last_value" in TsDigest Key: IOTDB-181 URL: https://issues.apache.org/jira/browse/IOTDB-181 Project: Apache IoTDB Issue Type: Improvement Reporter: Jialin Qiao In TsDigest, we have five statistics: min_value, max_value, sum_value, first_value, last_value. When filtering page or chunk, we use min_value and max_value for a filter like "s1>10" or "s1<20". The sum value can be used in aggregation query "select sum(s1) from root...". However, it is difficult for me to come up with a scenario that uses "first_value" and "last_value" to filter data, and they are never used at all... So why not remove them? -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-180) Get rid of JSON format in "show timeseries"
Jialin Qiao created IOTDB-180: - Summary: Get rid of JSON format in "show timeseries" Key: IOTDB-180 URL: https://issues.apache.org/jira/browse/IOTDB-180 Project: Apache IoTDB Issue Type: Wish Reporter: Jialin Qiao Attachments: image-2019-08-27-09-56-20-654.png, image-2019-08-27-09-56-28-577.png Currently, "show timeseries" prints result in JSON format, which is not friendly compared to "show timeseries root" in table format. !image-2019-08-27-09-56-20-654.png|width=463,height=538! !image-2019-08-27-09-56-28-577.png|width=694,height=458! Intuitively, I would expect that "show timeseries" works as "show timeseries root". Therefore, when users input a "show timeseries", I suggest that we treat it as "show timeseries root" and print results in table format. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-179) Add create matadata interfaces to Session
Jialin Qiao created IOTDB-179: - Summary: Add create matadata interfaces to Session Key: IOTDB-179 URL: https://issues.apache.org/jira/browse/IOTDB-179 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Only insertBatch() is supported in Session, we need more efficient interfaces. The first are "set storage group to XXX" and "create timeseries..." -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IOTDB-166) Update the download section (for v0.8) of the official website
[ https://issues.apache.org/jira/browse/IOTDB-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiangdong Huang closed IOTDB-166. - Assignee: xiangdong Huang Resolution: Won't Fix The issue is broken by #176 and #175. Now 0.7.0's download url is reserved. > Update the download section (for v0.8) of the official website > --- > > Key: IOTDB-166 > URL: https://issues.apache.org/jira/browse/IOTDB-166 > Project: Apache IoTDB > Issue Type: Task >Reporter: xiangdong Huang >Assignee: xiangdong Huang >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Once the v0.8.0 is released, we can update the download section in the > official website. > As v0.7 is not an apache official version, I think it can be removed. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-178) Cache hit Rate statistics
xiangdong Huang created IOTDB-178: - Summary: Cache hit Rate statistics Key: IOTDB-178 URL: https://issues.apache.org/jira/browse/IOTDB-178 Project: Apache IoTDB Issue Type: New Feature Reporter: xiangdong Huang As there are several cache structures in IoTDB for supporting fast querying, it is good if we can get the cache hit rate. The data can help us improving the query process of IoTDB. Currently, the caches are (According to [~Lei Rui] 's analysis): * TsFileMetaDataCache * DeviceMetadtaCache * FileReaderManager.closedFileReaderMap * ChunkLoader.chunkCache -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-177) 编译源代码时出现异常
邢质坦 created IOTDB-177: - Summary: 编译源代码时出现异常 Key: IOTDB-177 URL: https://issues.apache.org/jira/browse/IOTDB-177 Project: Apache IoTDB Issue Type: Bug Environment: CentOS 7.6 java version "1.8.0_212" Java(TM) SE Runtime Environment (build 1.8.0_212-b10) Java HotSpot(TM) 64-Bit Server VM (build 25.212-b10, mixed mode) Apache Maven 3.0.5 (Red Hat 3.0.5-17) Reporter: 邢质坦 # git clone https://github.com/apache/incubator-iotdb # cd incubator-iotdb #mvn clean install -DskipTests [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Apache IoTDB (incubating) Project Parent POM [INFO] TsFile [INFO] Service-rpc [INFO] IoTDB Jdbc [INFO] IoTDB Session [INFO] IoTDB Client [INFO] IoTDB Server [INFO] IoTDB Examples [INFO] IoTDB-Kafka Examples [INFO] IoTDB-RocketMQ Examples [INFO] client-example [INFO] tsfile-example [INFO] IoTDB Grafana [INFO] IoTDB Spark-TsFile [INFO] IoTDB Distribution [INFO] [INFO] [INFO] Building Apache IoTDB (incubating) Project Parent POM 0.9.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ iotdb-parent --- [INFO] Deleting /opt/incubator-iotdb/target [INFO] [INFO] --- maven-checkstyle-plugin:3.0.0:check (validate) @ iotdb-parent --- [INFO] [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven-version) @ iotdb-parent --- [INFO] [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-version-convergence) @ iotdb-parent --- [INFO] [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (vulnerability-checks) @ iotdb-parent --- [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache IoTDB (incubating) Project Parent POM .. FAILURE [2.244s] [INFO] TsFile SKIPPED [INFO] Service-rpc ... SKIPPED [INFO] IoTDB Jdbc SKIPPED [INFO] IoTDB Session . SKIPPED [INFO] IoTDB Client .. SKIPPED [INFO] IoTDB Server .. SKIPPED [INFO] IoTDB Examples SKIPPED [INFO] IoTDB-Kafka Examples .. SKIPPED [INFO] IoTDB-RocketMQ Examples ... SKIPPED [INFO] client-example SKIPPED [INFO] tsfile-example SKIPPED [INFO] IoTDB Grafana . SKIPPED [INFO] IoTDB Spark-TsFile SKIPPED [INFO] IoTDB Distribution SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.652s [INFO] Finished at: Mon Aug 26 17:12:13 CST 2019 [INFO] Final Memory: 18M/260M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce (vulnerability-checks) on project iotdb-parent: Execution vulnerability-checks of goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce failed: Failed to lookup component: ComponentReportAssistant: java.util.NoSuchElementException [ERROR] role: org.sonatype.ossindex.maven.common.ComponentReportAssistant [ERROR] roleHint: [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (IOTDB-173) Add rpc interface to insert data
[ https://issues.apache.org/jira/browse/IOTDB-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-173. - > Add rpc interface to insert data > > > Key: IOTDB-173 > URL: https://issues.apache.org/jira/browse/IOTDB-173 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Priority: Major > Labels: pull-request-available > Fix For: 0.9.0 > > Attachments: image-2019-08-23-12-20-32-821.png > > Time Spent: 10m > Remaining Estimate: 0h > > I used Jprofiler to profile the executBatch jdbc interface when inserting > data, and found 70% of the time cost is parsing SQL by Antlr3. > !image-2019-08-23-12-20-32-821.png! > To accelerate the insertion speed, a new interface that bypasses SQL is > needed. > One way is to add an RPC interface for batch insert, and I am working on that. -- This message was sent by Atlassian Jira (v8.3.2#803003)
