Hi，
1. 差值分段
2. 条件分段
3. 会话分段
I think the best choices are the direct translations. BTW, why we choose the
word 'series' in GROUP BY SERIES clause? It's more likely an aggregation
crossing different timeseries, like GROUP BY LEVEL and GROUP BY TAG.
发件人: ycy wi
日期: 星期四, 2023年2月23日
Congratulations, Rongzhao!
发件人: Jialin Qiao
日期: 星期三, 2023年1月4日 17:10
收件人: dev@iotdb.apache.org
主题: new committer: Rongzhao Chen
Hi,
The Project Management Committee (PMC) for Apache IoTDB
has invited Rongzhao Chen to become a committer and we are pleased
to announce that he has accepted.
Using a unified architecture is a convenient way to learn and expand IoTDB
indeed. If so, we should consider the extra resource cost in edge environment,
which may need more test in later versions. For example, a 4G4C docker
container can support X timeseries and Y QPS in a single process
Hi,
1. Can USING clause be optional, which is compatible with older versions?
Without using this clause means that IoTDB will search the class in the default
ext/udf directory.
2. The ‘jarLocation’defined in .g4 file is as follow:
USING ((FILE fileName=STRING_LITERAL) | URI uri)
I
For temporarily removing StandaloneMppIT, just changing
.github/workflows/standalone-it-for-mpp.yml is OK? I think it’s not necessary
removing the profile from pom.xml or the category annotation from *IT files.
发件人: Yuan Tian
日期: 星期四, 2022年10月20日 11:56
收件人: dev
主题: Remove old version
Wow, it will be a big event in IoTDB history. We have waited for the moment in
almost 1 year :)
BTW,
1. what's the time plan of the code frozen of v1.0.0? We should let all the
contributors know the close time of new features accepted window.
2. And are there any APIs, including SQL, Session
Hi,
Commit ID is really important in distribution, especially in testing/online
environment debugging. However, I think it's more convenient to query it
through CLI, not only including the commit id in a server-side file.
What's more, if we only rely on the head commit id, when a IoTDB
Hi,
I have finished the development of a new feature, aggregation by tags, under
the collaboration with @JonWang. I’m looking for someone to help to review
theses codes.
https://github.com/apache/iotdb/pull/6661
The main changes are
1. Support the basic function of aggregation query by
will be automatically migrated
to the new region?
Currently, no.
But we could also migrate some existing data by some sql.
2. Does the prefixPath must be a storage group name, or any arbitrary
prefix path?
Yes.
Thanks,
Jialin Qiao
Eric Pai 于2022年8月18日周四 11:00写
Hi,
Could you explain what will happen after a region being created manually in
detail? And I have some questions about this SQL
1. Does the exist data under the prefixPath will be automatically migrated to
the new region?
2. Does the prefixPath must be a storage group name, or any arbitrary
Got it. And we can change xxx-env.sh and xxx-env.bat with a wildcard classpath
parameter to simplify the command.
The original classpath param is like this: lib/a.jar:lib/b.jar
It can be replaced by: lib/*
And please remember to test well both in Unix and Windows~
在 2022/7/6 16:59，“SpriCoder”
Where's the lib folder? A single one to share or just duplicated for each
other?
在 2022/7/6 12:04，“SpriCoder” 写入:
To more specific:
In Choice 1, folders in apache-iotdb-0.14.0-SNAPSHOT-all-bin will like that:
├── sbin
├── conf
├── config
├── data
├── ext
├──
This is really a good feature!
Unlike relational database query, the 'column' name in IoTDB is a string
concatenated by the prefix path in FROM clause and the suffix path in SELECT
clause. In some cases maybe there are more than 1 output columns. If so, does
one simple HAVING clause still work
Great! Let's wake up those tags!
在 2022/6/24 16:42，“Wz” 写入:
Hi guys,
To handle multidimensional queries, we plan to implement data filtering and
aggregation on top of the MPP framework. Here's a description of the scenario:
Good news! How about '0.14.0-preview' ? As in general development we always use
*-alpha as an internal test version with all main features present. As the
description of the version, it mainly contains the new cluster.
在 2022/6/22 16:44，“Jialin Qiao” 写入:
Hi all,
It has been 4~5
%2FDtOJb%2BFuSP57tatrT4%3Dreserved=0
gives the details. I wonder if
I have to place the doc to somewhere else?
Eric Pai 于2022年6月21日周二 09:50写道：
> Got it! If we use shell script, we should consider both mac/Linux/Windows
> environment, as we have lots of developers using W
I think we may meet the requirements of matching 0-1 level in the future, then
*** may be not a good design.
As a single * stands for exactly 1 level now, we can define *{start, end} to
[start, end) levels, {x} to exactly x levels and {*} to arbitrary levels, where
** is just a short
pre-commit pipeline.
Eric Pai 于2022年6月20日周一 20:55写道：
> This is a very helpful tool for developers!
>
> In IoTDB we have not only code formatter, the spotless, but also the code
> linter, checkstyle. In maven we can run ‘mvn validate‘ to run checks of
This is a very helpful tool for developers!
In IoTDB we have not only code formatter, the spotless, but also the code
linter, checkstyle. In maven we can run ‘mvn validate‘ to run checks of both
the linter and formatter, or 'mvn validate -pl ' to check one or
more particular modules. However,
Good idea! If we can make use of the tags not only in metadata but also in data
query, we can enrich the data analysis ability a lot, and help the business
layer to achieve more goals than before. However as the query grammar may
become more complicated, we should take the easy-use into
If one region is under migration, what the output will be? Do we need a
state/status field?
在 2022/6/14 17:31，“Jialin Qiao” 写入:
Hi,
I created an issue to query the region distribution [1].
This could be used in some scenarios:
(1) To see if the region migration is successful
Thanks for your contribution! @dafei1288 This PR has been merged.
在 2022/6/9 18:45，“Jialin Qiao” 写入:
Welcome, Jiaqi!
—
Jialin Qiao
Apache IoTDB PMC
于2022年6月9日周四 12:42写道：
> Hello, everyone. Hope you are doing well. This is my first time PR in
>
Wow, I think this is very interesting to link relational model to our
timeseries model.
Could you give some examples about how to map timeseries to tables and columns?
In my brief study about Druid, it seems that for a particular measurement of
thousands of devices, it may be a wild table with
on the given node
omitting [-node ] and [--all-nodes] equals [-node 127.0.0.1]
--all-nodes and -node are mutually exclusive
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Eric Pai 于2022年5月23日周
+1. It's not necessary to give 2 different syntax but with same meaning. Just
define the most suitable one.
在 2022/5/23 11:22，“Haonan Hou” 写入:
Hi,
+1 for `FLUSH ALL` syntax.
`FLUSH` and `FLUSH sg` are the existing syntax of the current standalone
version.
If we execute
Maybe ALL and CLUSTER are keywords afterwards. We should use FLUSH `all` and
FLUSH `cluster` instead.
在 2022/5/23 11:16，“Xiangdong Huang” 写入:
how about if there is a sg called "all" or "cluster" ?
---
Xiangdong Huang
School of Software, Tsinghua
Good work. After this patch is applied, could this
issue(https://github.com/apache/iotdb/pull/5760) be solved properly?
在 2022/5/12 15:22，“廖兰宇”<181250...@smail.nju.edu.cn> 写入:
Hi everybody,
We defined some complex syntax in ordered to be compatible with the older
version. We are
+1, and as old cluster functions are deprecated, we can also disable and delete
the test cases of old cluster to accelerate CI.
在 2022/5/10 14:56，“Haonan Hou” 写入:
Hi,
Since our new cluster version is under developing and the basic features
have been implemented, I think
it’s time
Hi, all,
The google-java-format is just a code formatter, which cannot apply some rules
to code semantic. Only a formatter cannot help codes become better.
So we plan to enable the linter, checkstyle, which has already been integrated
in the validation stage to let the codes developed by
Excellent work! Now our query is more completed and can support more real world
requirements! Besides the feature, the GroupByFillDataSet is almostly decoupled
from GroupByEngineDataSet. Now I can develop the UDF nesting aggregations in
GROUP BY FILL query easily __
在 2021/12/27
Dear all,
A new feature, the ability of nesting expressions outside aggregation
functions, has been finished in master branch. Now we can query like this:
* Nested arbitrary expressions outside aggregation queries: select sum(s1)
+ sum(s2), -sum(s3), sum(s4) , sin(sum(s4) + cos(avg(s4)) +
Hi,
I have found serval bugs about the query result being not as expected in
cluster mode, but no critical bugs(node halt/data loss/tsfile corruption). They
can be fixed before v0.12.4 released. I think we should release v0.12.3 as soon
as possible.
-邮件原件-
发件人: Xiangdong Huang
发送时间:
I may be able to answer your question about the intention of the IT framework,
as we have already had benefit from it.
The biggest advantage of the IT framework is to REUSE our existing IT cases in
different cluster modes. Although the E2E test based on the test-container
technology can test
,
---
Houliang Qi
BONC, Ltd
On 11/10/2021 12:35，Junqing Wang wrote：
Agree with Eric Pai.
The quality of the cluster version is very important. For now, we should
focus more on quality rather than new architecture. Without the quality,
the cluster version is hard to use
to keep the competitive power ,
such as the InfluxDB which have already gone into action, So taking precautions
to urgent.
I will plan to create a new branch for the next architecture for POC in
parallel, welcome to join us to make IoTDB great!
宋秉华
songbing...@iie.ac.cn
From: Eric
Hi,
It's nice to plan next generation architecture of IoTDB.
However, before we start to design and discuss the refinement and optimization,
we should ensure the cluster quality as our expected. In our inner test, by
replaying the existed IT cases in a cluster environment, we have found many
+1
I think that every contributor in our community is glad to help other ones to
discuss solutions and review codes. And I have some ideas to improve peer
collaboration.
1. If the issue/pull request creator is familiar with the codes, he can use the
`git blame` tool to find the previous code
Hi, all,
The result set our ALIGEND BY DEVICE query returns contains two important
columns: timestamp and device.
See the implementation of AlignByDeviceDataSet
Hi, all,
I saw this JIRA https://issues.apache.org/jira/browse/IOTDB-1818 had been
finished without any discussions. But I still have some questions about the
daily dependency update mechanism.
According to the introduction
Hi,
As it's a critical bug fix, a patch version is necessary. +1 for releasing
v0.12.3.
Maybe we can publish a release schedule calendar in github or some other pages
__, thus everyone will know the whole roadmap and milestones.
在 2021/9/16 下午4:42，“Jialin Qiao” 写入:
Hi,
Release big
Hi,
It's very nice that we have so many incoming fixes, but should we make the
patch version be released at a fixed schedule, i.e. 2 weeks or 4 weeks, if no
critical bug is fixed?
I think the benefit is making all the community contributors and new version
pioneers know when to release next
. by default, electionRandomTimeOutMs can be 50 ms or something like
heartbeat/10 ?
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Eric Pai 于2021年8月23日周一 上午10:18写道：
>
> Hi, Xiangdong,
>
> So what your suggestions about
Hi, Xiangdong,
Supporting hostname is really a good feature! However, we should consider these
cons carefully:
1. DNS request is an additional cost in nodes communication. In cloud
environment, the latency may be as large as hundreds of milliseconds(e.g.
across available regions), and local
Hi, Xiangdong,
So what your suggestions about the election waiting time? Add another
configuration parameter called election_wait_time_ms, or left as a shorter
hardcode constant?
发件人: Eric Pai
日期: 2021年8月21日 星期六 下午7:32
收件人: "dev@iotdb.apache.org"
主题: 回复: Conclusion about JIRA i
Hi, all,
Now the randomElectionWait time is hardcode as 3-5s, which is not suitable when
the heartbeat_interval_ms and election_timeout_ms is too small.
I decide to change it to [2* heartbeat_interval_ms, 2* heartbeat_interval_ms +
50ms).
The 50ms is referred from the Raft paper with a low
45 matches
Mail list logo
