[jira] [Closed] (IOTDB-550) TSMRWriteExample executes unsuccessfully
[ https://issues.apache.org/jira/browse/IOTDB-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zesong Sun closed IOTDB-550. Resolution: Fixed > TSMRWriteExample executes unsuccessfully > > > Key: IOTDB-550 > URL: https://issues.apache.org/jira/browse/IOTDB-550 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Hadoop-TsFile >Affects Versions: 0.9.0, 0.9.1 >Reporter: Zesong Sun >Assignee: Zesong Sun >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > When running TSMRWriteExample, "Execute unsuccessfully" is printed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-550) TSMRWriteExample executes unsuccessfully
Zesong Sun created IOTDB-550: Summary: TSMRWriteExample executes unsuccessfully Key: IOTDB-550 URL: https://issues.apache.org/jira/browse/IOTDB-550 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Hadoop-TsFile Affects Versions: 0.9.1, 0.9.0 Reporter: Zesong Sun Assignee: Zesong Sun When running TSMRWriteExample, "Execute unsuccessfully" is printed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-546) Show child paths statement doesn't show quotation marks in path
Zesong Sun created IOTDB-546:
Summary: Show child paths statement doesn't show quotation marks
in path
Key: IOTDB-546
URL: https://issues.apache.org/jira/browse/IOTDB-546
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.10.0-SNAPSHOT
Reporter: Zesong Sun
Assignee: Zesong Sun
Fix For: 0.10.0-SNAPSHOT
When executing `show child paths` statement, the quotation marks in path don't
show. For example, if there is a path named {code}root.sg1.d1."1.2.3"{code}
The result will be:
{code}
IoTDB> SHOW CHILD PATHS root.sg.d1
+--+
| child paths|
+--+
|root.sg.d1.1.2.3|
+--+
Total line number = 1
It costs 0.090s
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-544) Apache IoTDB integration with more powerful aggregation index
[ https://issues.apache.org/jira/browse/IOTDB-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051779#comment-17051779 ] Zesong Sun commented on IOTDB-544: -- Hi, I'm quite interested in index and summary information optimization. I'd like to try my best in contributing to it. Thanks, Sun Zesong > Apache IoTDB integration with more powerful aggregation index > - > > Key: IOTDB-544 > URL: https://issues.apache.org/jira/browse/IOTDB-544 > Project: Apache IoTDB > Issue Type: Wish > Components: Core/Engine >Reporter: Xiangdong Huang >Priority: Major > Labels: IoTDB, gsoc2020, mentor > > IoTDB is a highly efficient time series database, which supports high speed > query process, including aggregation query. > Currently, IoTDB pre-calculates the aggregation info, or called the summary > info, (sum, count, max_time, min_time, max_value, min_value) for each page > and each Chunk. The info is helpful for aggregation operations and some query > filters. For example, if the query filter is value >10 and the max value of a > page is 9, we can skip the page. For another example, if the query is select > max(value) and the max value of 3 chunks are 5, 10, 20, then the max(value) > is 20. > However, there are two drawbacks: > 1. The summary info actually reduces the data that needs to be scanned as 1/k > (suppose each page has k data points). However, the time complexity is still > O(N). If we store a long historical data, e.g., storing 2 years data with > 500KHz, then the aggregation operation may be still time-consuming. So, a > tree-based index to reduce the time complexity from O(N) to O(logN) is a good > choice. Some basic ideas have been published in [1], while it can just handle > data with fix frequency. So, improving it and implementing it into IoTDB is a > good choice. > 2. The summary info is helpless for evaluating the query like where value >8 > if the max value = 10. If we can enrich the summary info, e.g., storing the > data histogram, we can use the histogram to evaluate how many points we can > return. > This proposal is mainly for adding an index for speeding up the aggregation > query. Besides, if we can let the summary info be more useful, it could be > better. > Notice that the premise is that the insertion speed should not be slow down > too much! > You should know: > • IoTDB query process > • TsFile structure and organization > • Basic index knowledge > • Java > difficulty: Major > mentors: > h...@apache.org > Reference: > [1] [https://www.sciencedirect.com/science/article/pii/S0306437918305489] > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-428) create a new timeseries by jdbc , system get back an error.
[ https://issues.apache.org/jira/browse/IOTDB-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17043138#comment-17043138 ] Zesong Sun commented on IOTDB-428: -- Hi, I think this is resulted by your data dir is not emptied. You could try to empty where you store data (both data files and system files). > create a new timeseries by jdbc , system get back an error. > > > Key: IOTDB-428 > URL: https://issues.apache.org/jira/browse/IOTDB-428 > Project: Apache IoTDB > Issue Type: Bug >Reporter: lming >Priority: Major > Labels: JDBC > > create a new timeseries by jdbc , system get back an error and warning user > there is a same timeseries already . so you couldn't create it.But this > timeseries is created first time. > It is correct of create timeseries in command line method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-329) MetricService not quite in Integration Tests (easy-fix, for fresh contributors)
[ https://issues.apache.org/jira/browse/IOTDB-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zesong Sun closed IOTDB-329. Resolution: Fixed > MetricService not quite in Integration Tests (easy-fix, for fresh > contributors) > --- > > Key: IOTDB-329 > URL: https://issues.apache.org/jira/browse/IOTDB-329 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.8.0, 0.9.0, 0.8.1 >Reporter: xiangdong Huang >Priority: Minor > Labels: easy-fix, pull-request-available > Attachments: image-2019-11-29-22-38-52-640.png > > Time Spent: 20m > Remaining Estimate: 0h > > There are some error infos on Travis: > !image-2019-11-29-22-38-52-640.png! > > It is because in our ITs, MetricService is not closed after an IT finished. > > It is quite easy to fix that, just add the code into > `EnvironmentUtils.cleanEnv()`: > ``` > MetricsService.getInstance().stop(); > ``` > before `cleanAllDir();` > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-274) Refactor MManager
[ https://issues.apache.org/jira/browse/IOTDB-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17033362#comment-17033362 ] Zesong Sun commented on IOTDB-274: -- Hi [~hxd], [~haonan], [~qiaojialin], Thanks for your opinions and help. I'd like to be responsible for this issue, and if you have other suggestions, please don't be hesitated to tell me. > Refactor MManager > -- > > Key: IOTDB-274 > URL: https://issues.apache.org/jira/browse/IOTDB-274 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Priority: Major > > The code of MManager needs to be refactored. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-452) Do all aggregations of one series at one pass in GroupBy
[ https://issues.apache.org/jira/browse/IOTDB-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029814#comment-17029814 ] Zesong Sun commented on IOTDB-452: -- Hi [~hxd], aggregations without group by clause is implemented in [this PR|https://github.com/apache/incubator-iotdb/pull/765]. With the development and improvement of query codes refactor, "group by clause" part is optimized today, so this new JIRA issue is opened for group by clause. > Do all aggregations of one series at one pass in GroupBy > > > Key: IOTDB-452 > URL: https://issues.apache.org/jira/browse/IOTDB-452 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Priority: Minor > > For example > > select avg(s1), count(s1), first(s1) from root.sg.d1 group by ([100,199],10ms) > > We could just construct one aggregate reader and get three aggregation > results at one pass. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-443) ReadOnlyMemChunk round float\double data incorrectly
[ https://issues.apache.org/jira/browse/IOTDB-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17028840#comment-17028840 ] Zesong Sun commented on IOTDB-443: -- If you need to fix this issue in your developing branch, you can cherry pick this commit id: 33a9604b0fde5a585ef7312687f707d1ef952ec6 > ReadOnlyMemChunk round float\double data incorrectly > > > Key: IOTDB-443 > URL: https://issues.apache.org/jira/browse/IOTDB-443 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Engine >Affects Versions: 0.9.1 >Reporter: Xiangdong Huang >Assignee: Zesong Sun >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > In our design, only RLE and TS_2DIFF need float_precision to round the value. > However, when we read data from memory, all float\double data will be > rounded, even if it uses Gorilla encoding. > e.g., suppose root.sg1.d1.s1 is double datatype and Gorilla encoding. The > float_precision=1. > If we insert a value (t,s1) = 1, 1.123, and select the data, we will get 1.1. > However, if we run `flush` after insert the data, and then select the data, > we will get 1.123. > > How to fix: we need to modify the init() method in ReadOnlyMemChunk to check > the encoding method first. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-393) Unclear error message for no privilege users
Zesong Sun created IOTDB-393:
Summary: Unclear error message for no privilege users
Key: IOTDB-393
URL: https://issues.apache.org/jira/browse/IOTDB-393
Project: Apache IoTDB
Issue Type: Bug
Reporter: Zesong Sun
Fix For: 0.10.0-SNAPSHOT
Attachments: WechatIMG12.png
When no privilege user try to set storage group or insert, the error message
should be more clear
Before:
{code}
Msg: INSERT / SET_STORAGE_GROUP / (no error message for query operation)
{code}
Change to:
{code}
Msg: No permissions for this operation INSERT / SET_STORAGE_GROUP / QUERY
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-369) [Query Optimization] Meet "Has not execute query" error when querying
Zesong Sun created IOTDB-369:
Summary: [Query Optimization] Meet "Has not execute query" error
when querying
Key: IOTDB-369
URL: https://issues.apache.org/jira/browse/IOTDB-369
Project: Apache IoTDB
Issue Type: Bug
Reporter: Zesong Sun
When querying original data, meet error of "Has not execute query":
{code}
IoTDB> select s0 from root.turbine.d1;
select s0 from root.turbine.d1;
+---+--+
| Time|root.turbine.d1.s0|
+---+--+
| 1970-01-01T08:00:00.001+08:00| 24.5|
+---+--+
Msg: Has not executed query
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-330) [Query Optimization] Improve the reading method of non-overlap unsequence data
Zesong Sun created IOTDB-330: Summary: [Query Optimization] Improve the reading method of non-overlap unsequence data Key: IOTDB-330 URL: https://issues.apache.org/jira/browse/IOTDB-330 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Currently, all unsequence chunk needs a reader during query, and if the chunks are not overlapped, only one reader is needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-304) Fix bug of incomplete HDFS URI
Zesong Sun created IOTDB-304: Summary: Fix bug of incomplete HDFS URI Key: IOTDB-304 URL: https://issues.apache.org/jira/browse/IOTDB-304 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.9.0 Reporter: Zesong Sun Attachments: WechatIMG3.png Fix bug of "Incomplete HDFS URI: no host" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-295) Refactor db.exception
Zesong Sun created IOTDB-295: Summary: Refactor db.exception Key: IOTDB-295 URL: https://issues.apache.org/jira/browse/IOTDB-295 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Fix For: 0.9.0-SNAPSHOT Refactor db.exception: * Extract uniform message into exception classes * Create base exception "ProcessException", which is extended by all exceptions * Add different error codes to all exceptions. When an exception is caught and a higher-level exception is thrown, the error code will keep and pass (so that users will know the detailed error reason) * Refactor packages under db.exception -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-271) Add security configuration for HDFS
Zesong Sun created IOTDB-271: Summary: Add security configuration for HDFS Key: IOTDB-271 URL: https://issues.apache.org/jira/browse/IOTDB-271 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Fix For: 0.9.0 Add security configuration for HDFS according to users' requirement. For example: "dfs.data.transfer.protection", "dfs.nameservices", "dfs.ha.namenodes.nameservice1", "dfs.namenode.rpc-address.nameservice1.nn1", "dfs.namenode.rpc-address.nameservice1.nn2", "dfs.client.failover.proxy.provider.nameservice2" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-270) Fix dropdown box of User Guide documents in official website
Zesong Sun created IOTDB-270: Summary: Fix dropdown box of User Guide documents in official website Key: IOTDB-270 URL: https://issues.apache.org/jira/browse/IOTDB-270 Project: Apache IoTDB Issue Type: Bug Reporter: Zesong Sun Fix For: 0.9.0 Change the external composition the dropdown box of User Guide documents in official website using to fix its wrong behavior in some browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-269) Refactor website Nav-bar structure
Zesong Sun created IOTDB-269: Summary: Refactor website Nav-bar structure Key: IOTDB-269 URL: https://issues.apache.org/jira/browse/IOTDB-269 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Attachments: new.png, old.png Currently, our official website has many separate documents part: Documents (Quick Start, User Guide, Other Materials, Frequently Asked Questions), Tools, Example... , which is quite complex for some users to find what they really want. What's more, the version control is also very confusing. We only support "in progress" documents for User Guide, and the documents for Tools and QuickStart are still 0.8.0. Therefore, I intend to refactor the website nav-bar structure, so that all documents for users that need version control are in the same page with only one entrance. Before refactoring: After refactoring: -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-258) Add documents for Shared Storage Architecture and Query History Visualization Tool
Zesong Sun created IOTDB-258: Summary: Add documents for Shared Storage Architecture and Query History Visualization Tool Key: IOTDB-258 URL: https://issues.apache.org/jira/browse/IOTDB-258 Project: Apache IoTDB Issue Type: New Feature Reporter: Zesong Sun Add documents for Shared Storage Architecture and Query History Visualization Tool -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-239) Add interface for showing devices
Zesong Sun created IOTDB-239: Summary: Add interface for showing devices Key: IOTDB-239 URL: https://issues.apache.org/jira/browse/IOTDB-239 Project: Apache IoTDB Issue Type: New Feature Reporter: Zesong Sun Create an interface for showing all the devices. USAGE: `SHOW DEVICES`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-234) Refactor TsFile storage on HDFS
Zesong Sun created IOTDB-234: Summary: Refactor TsFile storage on HDFS Key: IOTDB-234 URL: https://issues.apache.org/jira/browse/IOTDB-234 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Refactor TsFile storage on HDFS codes: * Extract the FileSystem factories into Hadoop module from TSFile module, so that TSFile module will not depend on Hadoop libs. * Use Java Reflection to get FileSystem factories in TSFile module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-222) Fix changing to read-only mode when flushing Tsfile on HDFS
Zesong Sun created IOTDB-222: Summary: Fix changing to read-only mode when flushing Tsfile on HDFS Key: IOTDB-222 URL: https://issues.apache.org/jira/browse/IOTDB-222 Project: Apache IoTDB Issue Type: Bug Reporter: Zesong Sun Attachments: WechatIMG20.png When flushing Tsfile on HDFS, system changes to read-only mode in some occasion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-219) Add config of tsfile_storage_fs in iotdb-engine.properties
Zesong Sun created IOTDB-219: Summary: Add config of tsfile_storage_fs in iotdb-engine.properties Key: IOTDB-219 URL: https://issues.apache.org/jira/browse/IOTDB-219 Project: Apache IoTDB Issue Type: Sub-task Reporter: Zesong Sun Add config of *tsfile_storage_fs* in iotdb-engine.properties for users -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-200) Support create TsFileWriter with config of storage file system
Zesong Sun created IOTDB-200: Summary: Support create TsFileWriter with config of storage file system Key: IOTDB-200 URL: https://issues.apache.org/jira/browse/IOTDB-200 Project: Apache IoTDB Issue Type: Sub-task Reporter: Zesong Sun This is the second step to resolve requirement [IOTDB-187|https://issues.apache.org/jira/browse/IOTDB-187]: "Enabling to choose storage in local file system or HDFS". This mainly affects Tsfile module. When users create *TsFileWriter*, they may choose to config where they'd like to store tsfile. Besides, IoTDB Engine should also check tsfile config before running, which ensure the config on tsfile and server is consistent. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-189) Support compatibility of HDFS file and java file
Zesong Sun created IOTDB-189: Summary: Support compatibility of HDFS file and java file Key: IOTDB-189 URL: https://issues.apache.org/jira/browse/IOTDB-189 Project: Apache IoTDB Issue Type: Sub-task Reporter: Zesong Sun Create "IoTDBFile", which supports compatibility of both HDFS file and java file -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-187) Enable to choose storage in local file system or HDFS
Zesong Sun created IOTDB-187: Summary: Enable to choose storage in local file system or HDFS Key: IOTDB-187 URL: https://issues.apache.org/jira/browse/IOTDB-187 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Enable to choose storage in local file system or HDFS "is_hdfs_storage=false" by default -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IOTDB-132) Add side navigator of documents
Zesong Sun created IOTDB-132: Summary: Add side navigator of documents Key: IOTDB-132 URL: https://issues.apache.org/jira/browse/IOTDB-132 Project: Apache IoTDB Issue Type: Improvement Reporter: Zesong Sun Since navigator on top of documents are changed into "Overview" part in [PR229|https://github.com/apache/incubator-iotdb/pull/229], a new navigator should be added on left side, which is more convenient and also consistent with User Guide documents. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IOTDB-127) Chinese version documents problems
Zesong Sun created IOTDB-127: Summary: Chinese version documents problems Key: IOTDB-127 URL: https://issues.apache.org/jira/browse/IOTDB-127 Project: Apache IoTDB Issue Type: Bug Reporter: Zesong Sun Hi, Since a "switch to Chinese" button is added on the document pages in [#PR219|[https://github.com/apache/incubator-iotdb/pull/219]], the Chinese version document does not follow the latest codes and English version docs. Here are some documents which Chinese version is missing: # IoTDB Examples # Reference/Research Papers # chap4/sec6 # Frequently Asked Questions # v0.7.0 Release Notes # Hadoop Connector Here are some documents which Chinese version has some problems: # chap4/sec1: Installation by Docker (Dockerfile) missing # chap4/sec2: Configuration part; some configuration variables that are changed in [this commit|[https://github.com/apache/incubator-iotdb/commit/3a16bd50517b303281a5c4a082c441770a8a4fe2]] # chap4/sec3: System Status Monitoring part, File Size Monitor part missing # chap4/sec4: some configuration variables that are changed in [this commit|[https://github.com/apache/incubator-iotdb/commit/3a16bd50517b303281a5c4a082c441770a8a4fe2]] # Quick Start：Install part, Configuration part # Grafana：simple-json-datasource part -- This message was sent by Atlassian JIRA (v7.6.3#76005)
