[BUILD-STABLE]: Job 'IoTDB/IoTDB-pip-new/master [master] [393]'
BUILD-STABLE: Job 'IoTDB/IoTDB-pip-new/master [master] [393]': Is back to normal.
[jira] [Created] (IOTDB-6244) Add new statistical aggreators include stddev and variance.
Zhihao Shen created IOTDB-6244: -- Summary: Add new statistical aggreators include stddev and variance. Key: IOTDB-6244 URL: https://issues.apache.org/jira/browse/IOTDB-6244 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Zhihao Shen Assignee: Zhihao Shen Fix For: 1.3.1 Many databases like MySQL, PostgreSQL, Trino and Doris have already support built-in statistical aggreators like stddev and variance, while currently IoTDB has not. Hence we decide to write similar aggreators to extends IoTDB's aggression functionality. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6242) Specify which datanode doesn't have udf jar
[ https://issues.apache.org/jira/browse/IOTDB-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6242: Assignee: Zhihao Shen > Specify which datanode doesn't have udf jar > --- > > Key: IOTDB-6242 > URL: https://issues.apache.org/jira/browse/IOTDB-6242 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Query >Reporter: Yuan Tian >Assignee: Zhihao Shen >Priority: Major > Attachments: image-2023-11-08-15-21-24-751.png > > > In cluster mode, if we need to create udf without specifying uri, we need to > make sure that each datanode has the jar in ext/udf, if not so, currently, we > will throw exception like following: > !image-2023-11-08-15-21-24-751.png! > > To be more user-friendly, we need to make the error msg more readable and > tell users which datanodes miss the udf jar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6243) Supporr time duration thredshold in fill(PREVIOUS) clause
Yuan Tian created IOTDB-6243: Summary: Supporr time duration thredshold in fill(PREVIOUS) clause Key: IOTDB-6243 URL: https://issues.apache.org/jira/browse/IOTDB-6243 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Currently, we fill any null value if there is an non-null value in the previous while we use fill(previous), however in some cases we want the null value keep null if the time duration between current value and previous non-null value exceed some specified thredshold. More details can been seen in https://apache-iotdb.feishu.cn/docx/M3RUdL3nGoKRbSxPmnscR9LJnGd -- This message was sent by Atlassian Jira (v8.20.10#820010)
