Hi,
I agree that the previous design and implementation of the monitor module have
many issues and we should redesign and refactor the code. The last PR#88 is
developed from early commit, which means its implementation is based on the
previous design. However, since recently we have many
Hi,
> We can make a release plan in the dev list first.
I read the document that Chris gave last month,
http://plc4x.apache.org/developers/release.html
In brief, there are four steps: (1) setting Maven configuration; (2)
creating the release branch and prepare the codebase; (3) mvn release and
Hi Xiangdong,
I think you can keep everyone posted by creating a refactoring breach
in the repo.
In this way it will save you some energy when you merge the PR from
other developer, as other developer can create their PR which is based
on your latest change.
Willem Jiang
Twitter: willemjiang
We can make a release plan in the dev list first.
>From my experience , there are lots of details need to go through in
the first preview version.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Mar 8, 2019 at 4:16 PM Xiangdong Huang wrote:
>
> That's Great! A binary release version
Sounds great!
From: Xiangdong Huang
Sent: Friday, March 8, 2019 12:16:18 AM
To: dev@iotdb.apache.org
Subject: Re: Do we have a plan to release the first normal version of IoTDB
this month?
That's Great! A binary release version is really needed!
And, if so, at
Hey,
Xiangdong Huang wrote:
> I think the use case you provided is valuable, I need to take a time to
> consider about how to support that better.
Sure, thanks for looking into it.
> By the way, can you tell me what `IRIs` is and what the Path looks like? If
> so, I can record it on the PR's
Hi,
The two class, FileNodeManager and FileNodeProcessor, are too large (more
than 3000 lines totally), and the logic is complex. But these two classes
play very very important roles in IoTDB.
Now, I decide to refactor the two classes to try to make it more clear and
guarantee the logic is
Hi,
I submit a PR https://github.com/apache/incubator-iotdb/pull/90 to fix the
UT issues caused by adding the float precision control feature.
All other PRs need to merge this modification, otherwise you may be not
able to pass the CI...
Best,
---
Xiangdong
Hi Marko,
I think the use case you provided is valuable, I need to take a time to
consider about how to support that better.
By the way, can you tell me what `IRIs` is and what the Path looks like? If
so, I can record it on the PR's explanation to let the PR more meaningful.
Best,
Hey,
Xiangdong Huang wrote:
> So, it is important for IoTDB to recognize which is the measurement name
> from a path. @Marko, that is why I said add a dot in the measurement will
> cause many modifications.
Right, I can only speak from a limited testing experience, where dots in
device and
Hi all,
I am LiuRui (second-year graduated student) from the IoTDB group. Recently am
working on the Monitor Module in IoTDB which is to store some monitoring
statistics like data file size and successfully ingested data point number into
an internal storage group (root.stats). Monitor module
Hi,
I temporary deactive the CI environment of Win10+OracleJDK11 on Travis,
because of the problem of Travis platform.
A PR is: https://github.com/apache/incubator-iotdb/pull/89
After the PR is merged. all unclosed PRs need to merge the latest master
branch to pass the Travis CI.
best,
That's Great! A binary release version is really needed!
And, if so, at least users can get iotdb-jdbc jars from Maven central
repository...
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Christofer Dutz 于2019年3月8日周五 下午3:29写道:
13 matches
Mail list logo