[GitHub] [iotdb-client-go] HTHou merged pull request #78: [To rel/0.13] session pool supports multiple nodes
HTHou merged PR #78: URL: https://github.com/apache/iotdb-client-go/pull/78 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-client-go] HTHou merged pull request #79: adds sessionPool
HTHou merged PR #79: URL: https://github.com/apache/iotdb-client-go/pull/79 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (IOTDB-4684) Devices with the same name but different alignment properties are compacted into the wrong alignment property
[ https://issues.apache.org/jira/browse/IOTDB-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698211#comment-17698211 ] 刘珍 commented on IOTDB-4684: --- 修复前版本 rc/1.0.1 0129版本 573097a !screenshot-1.png! 修复后版本rc/1.1.0 0306 32f9db0 !screenshot-2.png! > Devices with the same name but different alignment properties are compacted > into the wrong alignment property > - > > Key: IOTDB-4684 > URL: https://issues.apache.org/jira/browse/IOTDB-4684 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.13.0 >Reporter: 周沛辰 >Assignee: 周沛辰 >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > Attachments: exec_4684.sh, iotdb_4684.conf, iotdb_4684_1.conf, > iotdb_4684_aligned.conf, screenshot-1.png, screenshot-2.png > > Original Estimate: 48h > Remaining Estimate: 48h > > *Description* > After the nonAligned device is deleted, an aligned device with the same name > is created, and it will be compacted into the nonAligned device after > compaction. > Similarly, after the aligned device is deleted, an nonAligned device with the > same name is created, and it will be compacted into the aligned device after > compaction. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5649) Refactor ExpressionAnalyzer using visitor pattern
[ https://issues.apache.org/jira/browse/IOTDB-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-5649: --- Assignee: LiYuheng (was: Minghui Liu) > Refactor ExpressionAnalyzer using visitor pattern > - > > Key: IOTDB-5649 > URL: https://issues.apache.org/jira/browse/IOTDB-5649 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Minghui Liu >Assignee: LiYuheng >Priority: Major > Labels: pull-request-available > Fix For: master branch > > > ExpressionAnalyzer is the class in charge of handling expressions. > Each method in this class has different ability, such as > searchSourceExpressions() finds out which sources the expression contains, > removeWildcardInExpression() remove * from expression, and so on. > There were some redundant logic in ExpressionAnalyzer's methods. To make it > easier to add new kinds of expressions, it's necessary to simplify. > After analyze the similarity between these methods, I believe the visitor > pattern is a good way to make it simple. The same logic can be contained in > superclass-visitor, and the difference can be implemented by > subclass-visitor's override. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5650) Pipe Plugin: From SQL to ConfigNode
伊丹翔 created IOTDB-5650: -- Summary: Pipe Plugin: From SQL to ConfigNode Key: IOTDB-5650 URL: https://issues.apache.org/jira/browse/IOTDB-5650 Project: Apache IoTDB Issue Type: Improvement Reporter: 伊丹翔 Assignee: 伊丹翔 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5649) Refactor ExpressionAnalyzer using visitor pattern
Minghui Liu created IOTDB-5649: -- Summary: Refactor ExpressionAnalyzer using visitor pattern Key: IOTDB-5649 URL: https://issues.apache.org/jira/browse/IOTDB-5649 Project: Apache IoTDB Issue Type: Improvement Reporter: Minghui Liu Assignee: Minghui Liu Fix For: master branch ExpressionAnalyzer is the class in charge of handling expressions. Each method in this class has different ability, such as searchSourceExpressions() finds out which sources the expression contains, removeWildcardInExpression() remove * from expression, and so on. There were some redundant logic in ExpressionAnalyzer's methods. To make it easier to add new kinds of expressions, it's necessary to simplify. After analyze the similarity between these methods, I believe the visitor pattern is a good way to make it simple. The same logic can be contained in superclass-visitor, and the difference can be implemented by subclass-visitor's override. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] fuliwen opened a new pull request, #79: adds sessionPool
fuliwen opened a new pull request, #79: URL: https://github.com/apache/iotdb-client-go/pull/79 adds sessionPool -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (IOTDB-5648) [doc]should show the value of IoTDB edition and language after user has been selected
changxue created IOTDB-5648: --- Summary: [doc]should show the value of IoTDB edition and language after user has been selected Key: IOTDB-5648 URL: https://issues.apache.org/jira/browse/IOTDB-5648 Project: Apache IoTDB Issue Type: Improvement Reporter: changxue Assignee: Haonan Hou Attachments: image-2023-03-09-09-50-53-134.png [doc]should show the value of IoTDB edition and language after user has been selected !image-2023-03-09-09-50-53-134.png|width=400! This would make it more clearly to user. expect: When I choose an edition of IoTDB , it shows the real edition of IoTDB e.g. latest, rather than "Documentation" or "文档" The same to language. Further more, if we could change the language for each user according to their own configurations of browser, it would be much better. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5522) Last Query performance improvement
[ https://issues.apache.org/jira/browse/IOTDB-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697935#comment-17697935 ] liaolanyu commented on IOTDB-5522: -- This doc describes what we think may slow down the last query: [https://apache-iotdb.feishu.cn/docx/GVe2d35aAoVYVhxnueac0hK9nUf] However, we found current last query might behave wrongly if multiple DataRegions of one timeseries exists on one DataNode. > Last Query performance improvement > -- > > Key: IOTDB-5522 > URL: https://issues.apache.org/jira/browse/IOTDB-5522 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Query >Reporter: Yuan Tian >Assignee: liaolanyu >Priority: Major > Attachments: image-2023-02-10-21-23-28-478.png, > image-2023-02-16-20-16-11-215.png > > > If we have a lot of data regions and then we execute `select last s1 from > root.sg.d1`, this sql may not execute that fast as we expected, because it > may need to wait for all data regions' result and then merge it. > In some user's case, we build a 1C9D cluster, we set dataregion per database > to 27. We need 300ms to get the last query result which even slower than > MatrixDB. > !image-2023-02-16-20-16-11-215.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5240) Missing schemaTemplateId in SchemaRegion snapshot
[
https://issues.apache.org/jira/browse/IOTDB-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697805#comment-17697805
]
changxue commented on IOTDB-5240:
-
reproduction:
1. append configs into iotdb-common.properties
{code}
config_node_ratis_snapshot_trigger_threshold=40
schema_region_ratis_snapshot_trigger_threshold=40
data_region_ratis_snapshot_trigger_threshold=40
{code}
2. start 3C3D IoTDB cluster
3. create a template named `IoTDB-5240`, 把它绑定到 1000
个各不相同的路径上(root.iotdb5240.*)，每个插入一条数据。
4. 查询其中一个device的数据：例如 root.iotdb5240.kc___999
5. restart the cluster with stop and start
6. 再次查询device的数据：root.iotdb5240.kc___999
7. 插入一条数据到 某个device : root.iotdb5240.kc___999
目前重启后查询数据为空（第6步），其他正常。
绑定如果达到5万，最后一个节点stop-datanode 后会导致vm问题或者机器内存问题。
> Missing schemaTemplateId in SchemaRegion snapshot
> -
>
> Key: IOTDB-5240
> URL: https://issues.apache.org/jira/browse/IOTDB-5240
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: Yukun Zhou
>Assignee: Yukun Zhou
>Priority: Major
> Labels: pull-request-available
> Fix For: master branch, 1.0.1
>
> Original Estimate: 16h
> Remaining Estimate: 16h
>
> Currently, the schemaTemplateId of device node is not stored in schemaRegion
> snapshot, which results in failure schema query and fetch after DataNode
> restart.
> Add template id to schema region snapshot
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5647) Multi-Model IMNode Management
yanze chen created IOTDB-5647: - Summary: Multi-Model IMNode Management Key: IOTDB-5647 URL: https://issues.apache.org/jira/browse/IOTDB-5647 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen https://apache-iotdb.feishu.cn/docx/JZhudIX6Vob7kxx62t2cWeeLnbb -- This message was sent by Atlassian Jira (v8.20.10#820010)
