[jira] [Assigned] (IOTDB-5948) Optimize some usage of map in write process
[ https://issues.apache.org/jira/browse/IOTDB-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5948: - Assignee: Haonan Hou Resolution: Fixed [https://github.com/apache/iotdb/pull/9878] > Optimize some usage of map in write process > --- > > Key: IOTDB-5948 > URL: https://issues.apache.org/jira/browse/IOTDB-5948 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Minor > > The getDataRegionReplicaSetForWriting method in DataPartition is inefficient. > We don't need a stream to collect TRegionReplicaSet from dataPartitionMap. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5948) Optimize some usage of map in write process
Haonan Hou created IOTDB-5948: - Summary: Optimize some usage of map in write process Key: IOTDB-5948 URL: https://issues.apache.org/jira/browse/IOTDB-5948 Project: Apache IoTDB Issue Type: Improvement Reporter: Haonan Hou -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5947) Optimize the AlignedTVList column check logic when insert
[ https://issues.apache.org/jira/browse/IOTDB-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5947: - Assignee: Haonan Hou > Optimize the AlignedTVList column check logic when insert > - > > Key: IOTDB-5947 > URL: https://issues.apache.org/jira/browse/IOTDB-5947 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > Fix For: 1.2.0 > > > Currently, one insert will calculate an int array to record index information > of AlignedTVList and values in InsertPlan. This calculation will traverse the > measurement list twice. > However, this logic can be simplified by traverse only once. We can just use > a new values Object array, move the origin values to this new array which > matches the order of the AlignedList, and then insert the new values into > TVList. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5947) Optimize the AlignedTVList column check logic when insert
Haonan Hou created IOTDB-5947: - Summary: Optimize the AlignedTVList column check logic when insert Key: IOTDB-5947 URL: https://issues.apache.org/jira/browse/IOTDB-5947 Project: Apache IoTDB Issue Type: Improvement Reporter: Haonan Hou Currently, one insert will calculate an int array to record index information of AlignedTVList and values in InsertPlan. This calculation will traverse the measurement list twice. However, this logic can be simplified by traverse only once. We can just use a new values Object array, move the origin values to this new array which matches the order of the AlignedList, and then insert the new values into TVList. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5946) Optimize the implement of tablet in Go client
[ https://issues.apache.org/jira/browse/IOTDB-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5946: - Assignee: Haonan Hou > Optimize the implement of tablet in Go client > - > > Key: IOTDB-5946 > URL: https://issues.apache.org/jira/browse/IOTDB-5946 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > > The implement of GO tablet is different with the JAVA version. > Go Tablet does not have the rowSize field and reset method of Java Tablet, so > each time the tablet setValue must be filled to the maximum number of rows on > the Tablet, and the Tablet cannot be reused after one insert. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5945) Add a cache to avoid initialize duplicated device id object in write process
[ https://issues.apache.org/jira/browse/IOTDB-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5945: - Assignee: Haonan Hou > Add a cache to avoid initialize duplicated device id object in write process > > > Key: IOTDB-5945 > URL: https://issues.apache.org/jira/browse/IOTDB-5945 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > > In write process, especially write by insertRecords interface, the > PartialPath Object of deviceId may init too many times. This PR is adding a > DataNodeDevicePathCache to avoid initialize duplicated PartialPath. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5945) Add a cache to avoid initialize duplicated device id object in write process
[ https://issues.apache.org/jira/browse/IOTDB-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727768#comment-17727768 ] Haonan Hou commented on IOTDB-5945: --- https://github.com/apache/iotdb/pull/9644 > Add a cache to avoid initialize duplicated device id object in write process > > > Key: IOTDB-5945 > URL: https://issues.apache.org/jira/browse/IOTDB-5945 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > > In write process, especially write by insertRecords interface, the > PartialPath Object of deviceId may init too many times. This PR is adding a > DataNodeDevicePathCache to avoid initialize duplicated PartialPath. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5945) Add a cache to avoid initialize duplicated device id object in write process
Haonan Hou created IOTDB-5945: - Summary: Add a cache to avoid initialize duplicated device id object in write process Key: IOTDB-5945 URL: https://issues.apache.org/jira/browse/IOTDB-5945 Project: Apache IoTDB Issue Type: Improvement Reporter: Haonan Hou In write process, especially write by insertRecords interface, the PartialPath Object of deviceId may init too many times. This PR is adding a DataNodeDevicePathCache to avoid initialize duplicated PartialPath. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5888) TTL logs didn't consider timestamp precision
[ https://issues.apache.org/jira/browse/IOTDB-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727767#comment-17727767 ] Haonan Hou commented on IOTDB-5888: --- https://github.com/apache/iotdb/pull/9870 > TTL logs didn't consider timestamp precision > > > Key: IOTDB-5888 > URL: https://issues.apache.org/jira/browse/IOTDB-5888 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0, 1.1.0 >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > Labels: pull-request-available > Fix For: 1.2.0 > > Attachments: image-2023-05-17-10-23-55-871.png > > > !image-2023-05-17-10-23-55-871.png|width=1108,height=421! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5888) TTL logs didn't consider timestamp precision
[ https://issues.apache.org/jira/browse/IOTDB-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727765#comment-17727765 ] Haonan Hou commented on IOTDB-5888: --- https://github.com/apache/iotdb/pull/9870 > TTL logs didn't consider timestamp precision > > > Key: IOTDB-5888 > URL: https://issues.apache.org/jira/browse/IOTDB-5888 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0, 1.1.0 >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > Labels: pull-request-available > Fix For: 1.2.0 > > Attachments: image-2023-05-17-10-23-55-871.png > > > !image-2023-05-17-10-23-55-871.png|width=1108,height=421! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5944) Follower doesn't need to update last cache when using IoT_consensus
[ https://issues.apache.org/jira/browse/IOTDB-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5944: - Assignee: Haonan Hou > Follower doesn't need to update last cache when using IoT_consensus > > > Key: IOTDB-5944 > URL: https://issues.apache.org/jira/browse/IOTDB-5944 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > > Currently, the Last cache on follower is not used for Last Query. Disabling > update last cache on follower can save some memory and improve the write > performance on follower node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5944) Follower doesn't need to update last cache when using IoT_consensus
Haonan Hou created IOTDB-5944: - Summary: Follower doesn't need to update last cache when using IoT_consensus Key: IOTDB-5944 URL: https://issues.apache.org/jira/browse/IOTDB-5944 Project: Apache IoTDB Issue Type: Improvement Reporter: Haonan Hou Currently, the Last cache on follower is not used for Last Query. Disabling update last cache on follower can save some memory and improve the write performance on follower node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5944) Follower doesn't need to update last cache when using IoT_consensus
[ https://issues.apache.org/jira/browse/IOTDB-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727763#comment-17727763 ] Haonan Hou commented on IOTDB-5944: --- https://github.com/apache/iotdb/pull/9811 > Follower doesn't need to update last cache when using IoT_consensus > > > Key: IOTDB-5944 > URL: https://issues.apache.org/jira/browse/IOTDB-5944 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Priority: Major > > Currently, the Last cache on follower is not used for Last Query. Disabling > update last cache on follower can save some memory and improve the write > performance on follower node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5943) Avoid rpc invoking for SimpleQueryTerminator when endpoint is local address
[ https://issues.apache.org/jira/browse/IOTDB-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727760#comment-17727760 ] Gaofei Cao commented on IOTDB-5943: --- Completed, link: https://github.com/apache/iotdb/pull/9927 > Avoid rpc invoking for SimpleQueryTerminator when endpoint is local address > --- > > Key: IOTDB-5943 > URL: https://issues.apache.org/jira/browse/IOTDB-5943 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Reporter: Gaofei Cao >Assignee: Gaofei Cao >Priority: Major > > In class SimpleQueryTerminator, there is no need to send RPC request for > local invoking. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5943) Avoid rpc invoking for SimpleQueryTerminator when endpoint is local address
Gaofei Cao created IOTDB-5943: - Summary: Avoid rpc invoking for SimpleQueryTerminator when endpoint is local address Key: IOTDB-5943 URL: https://issues.apache.org/jira/browse/IOTDB-5943 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Gaofei Cao Assignee: Gaofei Cao In class SimpleQueryTerminator, there is no need to send RPC request for local invoking. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] dependabot[bot] closed pull request #84: Bump github.com/stretchr/testify from 1.8.2 to 1.8.3
dependabot[bot] closed pull request #84: Bump github.com/stretchr/testify from 1.8.2 to 1.8.3 URL: https://github.com/apache/iotdb-client-go/pull/84 -- 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] dependabot[bot] opened a new pull request, #87: Bump github.com/stretchr/testify from 1.8.2 to 1.8.4
dependabot[bot] opened a new pull request, #87: URL: https://github.com/apache/iotdb-client-go/pull/87 Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.8.2 to 1.8.4. Commits https://github.com/stretchr/testify/commit/f97607b89807936ac4ff96748d766cf4b9711f78;>f97607b Create GitHub release when new release tag is pushed (https://redirect.github.com/stretchr/testify/issues/1354;>#1354) https://github.com/stretchr/testify/commit/4c93d8f201cb46ed50de949ee65804f944b570f8;>4c93d8f EqualExportedValues: Handle nested pointer, slice and map fields (https://redirect.github.com/stretchr/testify/issues/1379;>#1379) https://github.com/stretchr/testify/commit/4b2f4d2bcff3848b6a4e63d462da6ce3c21e9c78;>4b2f4d2 add EventuallyWithT assertion (https://redirect.github.com/stretchr/testify/issues/1264;>#1264) https://github.com/stretchr/testify/commit/b3106d772c7aa439743e1a3f4de81149e323cf70;>b3106d7 allow testing for functional options (https://redirect.github.com/stretchr/testify/issues/1023;>#1023) https://github.com/stretchr/testify/commit/437071b948cd89bdbaaf43a41f19fbe1a0945f6f;>437071b assert: fix error message formatting for NotContains (https://redirect.github.com/stretchr/testify/issues/1362;>#1362) https://github.com/stretchr/testify/commit/c5fc9d6b6b21ea89be8480c0dc35e2977ab988f6;>c5fc9d6 Compare public elements of struct (https://redirect.github.com/stretchr/testify/issues/1309;>#1309) See full diff in https://github.com/stretchr/testify/compare/v1.8.2...v1.8.4;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] dependabot[bot] commented on pull request #84: Bump github.com/stretchr/testify from 1.8.2 to 1.8.3
dependabot[bot] commented on PR #84: URL: https://github.com/apache/iotdb-client-go/pull/84#issuecomment-1569376447 Superseded by #87. -- 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-5942) Pipe: Fix bugs in PipeWALResourceManager, EnrichedEvent, IoTDBThriftReceiverV1
yusicheng created IOTDB-5942: Summary: Pipe: Fix bugs in PipeWALResourceManager, EnrichedEvent, IoTDBThriftReceiverV1 Key: IOTDB-5942 URL: https://issues.apache.org/jira/browse/IOTDB-5942 Project: Apache IoTDB Issue Type: Task Reporter: yusicheng Assignee: yusicheng - fix bugs in PipeWALResourceManager: Concurrent modification exception when check WAL TTL - fix bugs in EnrichedEvent: PipeRealtimeCollectEvent reference count error - fix bugs in IoTDBThriftReceiverV1: Writer stream closed because of tsfile with the same name - add log when reporting PipeException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5941) Same Column in one group by level query
Yuan Tian created IOTDB-5941: Summary: Same Column in one group by level query Key: IOTDB-5941 URL: https://issues.apache.org/jira/browse/IOTDB-5941 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: 李伟豪 初始化数据如下: insert into root.ln.wf01.wt01(timestamp,temp1)values(0,21); insert into root.ln.wf01.wt01(timestamp,temp1)values(360,22); insert into root.ln.wf01.wt01(timestamp,temp2)values(0,23); insert into root.ln.wf01.wt01(timestamp,temp2)values(360,24); insert into root.ln.wf01.wt02(timestamp,temp1)values(0,25); insert into root.ln.wf01.wt02(timestamp,temp1)values(360,26); insert into root.ln.wf01.wt02(timestamp,temp2)values(0,27); insert into root.ln.wf01.wt02(timestamp,temp2)values(360,28); insert into root.ln.wf01.wt03(timestamp,temp1)values(0,29); insert into root.ln.wf01.wt03(timestamp,temp1)values(360,30); insert into root.ln.wf01.wt03(timestamp,temp2)values(0,31); insert into root.ln.wf01.wt03(timestamp,temp2)values(360,32); 查询sql: select avg(temp1) from root.ln.wf01.wt03, root.ln.wf01.wt01 group by ([1970-01-01T08:00:00,1970-01-01T10:00:00),1h),level=2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5940) Added old sync connector for IoTDB Pipe
[ https://issues.apache.org/jira/browse/IOTDB-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 陈哲涵 reassigned IOTDB-5940: -- Assignee: 陈哲涵 > Added old sync connector for IoTDB Pipe > --- > > Key: IOTDB-5940 > URL: https://issues.apache.org/jira/browse/IOTDB-5940 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: 陈哲涵 >Assignee: 陈哲涵 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5940) Added old sync connector for IoTDB Pipe
陈哲涵 created IOTDB-5940: -- Summary: Added old sync connector for IoTDB Pipe Key: IOTDB-5940 URL: https://issues.apache.org/jira/browse/IOTDB-5940 Project: Apache IoTDB Issue Type: New Feature Reporter: 陈哲涵 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5939) Flusing Task Timeout Detect Thread always use default timeout parameter as its timeout
Yuan Tian created IOTDB-5939: Summary: Flusing Task Timeout Detect Thread always use default timeout parameter as its timeout Key: IOTDB-5939 URL: https://issues.apache.org/jira/browse/IOTDB-5939 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Flusing Task Timeout Detect Thread should use timeout in session instead of default timeout parameter as its timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
