Re: The community is becoming better and better

[Xin Wang]

IOT is now one of the most important scenes, especially in the 5G era. Keep
going, dear guys.

- Xin

Dawei Liu  于2020年2月17日周一 下午11:21写道：

> Hi，
>
> Congretulations! I come from NAVINFO company and am also interested IoTDB.
>
> Now I am working on the Storage engine and query engine refactor.
>
> It is a good experience to see IoTDB's growth under all of our community
> effort.
>
>
> Thanks,
> ---
> Dawei Liu
>
>
>
> > 2020年2月17日 下午10:54，Xiangdong Huang  写道：
> >
> > Hi all,
> >
> > I am glad to see both RocketMQ and Flink committers submitted several PRs
> > to IOTDB. e.g.[1]
> >
> > It is a good signal to indicate our community is becoming better and
> > better.
> >
> > [1] https://github.com/apache/incubator-iotdb/pull/817
> >
> > Cheers,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
>
>

-- 
Thanks,
Xin

Re: The community is becoming better and better

[Xin Wang]

Thanks. I'm glad to work with you to make our community better and better.

-Xin

Jialin Qiao  于2020年2月18日周二 上午11:31写道：

> Hi Xin,
>
> Welcome! Hope we could give a set of solutions for IoT data from collect,
> process to storage.
>
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> > -原始邮件-
> > 发件人: "Xin Wang" 
> > 发送时间: 2020-02-18 11:14:23 (星期二)
> > 收件人: dev@iotdb.apache.org
> > 抄送:
> > 主题: Re: The community is becoming better and better
> >
> > IOT is now one of the most important scenes, especially in the 5G era.
> Keep
> > going, dear guys.
> >
> > - Xin
> >
> > Dawei Liu  于2020年2月17日周一 下午11:21写道：
> >
> > > Hi，
> > >
> > > Congretulations! I come from NAVINFO company and am also interested
> IoTDB.
> > >
> > > Now I am working on the Storage engine and query engine refactor.
> > >
> > > It is a good experience to see IoTDB's growth under all of our
> community
> > > effort.
> > >
> > >
> > > Thanks,
> > > ---
> > > Dawei Liu
> > >
> > >
> > >
> > > > 2020年2月17日 下午10:54，Xiangdong Huang  写道：
> > > >
> > > > Hi all,
> > > >
> > > > I am glad to see both RocketMQ and Flink committers submitted
> several PRs
> > > > to IOTDB. e.g.[1]
> > > >
> > > > It is a good signal to indicate our community is becoming better and
> > > > better.
> > > >
> > > > [1] https://github.com/apache/incubator-iotdb/pull/817
> > > >
> > > > Cheers,
> > > > ---
> > > > Xiangdong Huang
> > > > School of Software, Tsinghua University
> > > >
> > > > 黄向东
> > > > 清华大学 软件学院
> > >
> > >
> >
> > --
> > Thanks,
> > Xin
>


-- 
Thanks,
Xin

Re: [DISCUSS] When Release 0.10.0

[Xin Wang]

Hi Xiangdong,

I see you mentioned distributed version of IoTDB.
In my opinion, distributed capability is very important for the use of
production environment, especially in the case of large amount of data,
 which should also be one of the focuses of the next phase of our project.

- Xin

Xiangdong Huang  于2020年2月15日周六 上午11:12写道：

> Hi,
>
> It's been a month since the last release.
> It is time to open this discussion again.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2020年1月14日周二 下午6:29写道：
>
> > Hi,
> >
> > > Refer to the temporary release note for `0.10.0-SNAPSHOT`,
> > auto-generated by JIRA [1].
> >
> > So we should not call the fixed version of an issue as "0.10.0-SNAPSHOT"
> > (and not "master branch"), it should be "0.10.0".
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Lei Rui  于2020年1月14日周二 上午10:20写道：
> >
> >> Hi,
> >>
> >>
> >> It has been almost two months since the release tag of `release/0.9.0`
> >> was created on Nov 23, 2019.
> >>
> >>
> >> 1. New changes that have taken place:
> >> Refer to the temporary release note for `0.10.0-SNAPSHOT`,
> auto-generated
> >> by JIRA [1].
> >> (about 16 bug fixes, 4 new features, 13 improvements)
> >>
> >>
> >> 2. Upcoming new changes:
> >> As far as I know, the develop team has been working towards two
> >> directions recently:
> >> 1. the distributed version of IoTDB
> >> 2. the refactor of both physical design and query processing
> >>
> >>
> >> Shall we withhold the release of 0.10.0 until the two upcoming changes
> >> are finished?
> >> What do you think?
> >>
> >>
> >>
> >> Regards,
> >> Lei Rui
> >>
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322720&version=12346616
> >>
> >>
>


-- 
Thanks,
Xin

Re: Balance the mailing list and JIRA notification

[Xin Wang]

It's a real problem. +1 for only forwarding Jira creation and comment.

- Xin

Jialin Qiao  于2020年3月6日周五 上午9:12写道：

> Hi,
>
> +1 for only forwarding Jira creation and comment.
>
> Stopping forwarding operations like closing issue, linking PR, assigning
> issue...
>
> Could we simplify the issue report format?
>
> Like this:
>
> @++
> [
> https://issues.apache.org/jira/browse/IOTDB-498?focusedWorklogId=397173&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-397173
> ]
>
> ASF GitHub Bot 在 IOTDB-498中添加了工作日志:
> 
>
> 作者: ASF GitHub Bot
> 创建于: 04/三月/20 01:45
> 开始日期: 04/三月/20 01:45
> 耗费时间: 10分
> 工作说明: qiaojialin commented on pull request #878: [IOTDB-498] Support date
> format "2020-02-10"
> URL: https://github.com/apache/incubator-iotdb/pull/878
>
> 
> 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.
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> @++
>
> The only useful information is only two lines:
>
> @++
> 工作说明: qiaojialin commented on pull request #878: [IOTDB-498] Support date
> format "2020-02-10"
> URL: https://github.com/apache/incubator-iotdb/pull/878
> @++
>
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> > -原始邮件-
> > 发件人: "Xiangdong Huang" 
> > 发送时间: 2020-03-06 08:46:02 (星期五)
> > 收件人: dev@iotdb.apache.org
> > 抄送:
> > 主题: Balance the mailing list and JIRA notification
> >
> > Hi all,
> >
> > In [1], Chirs pointed out that "most email traffic generated by jira
> (hard
> > to follow especially when trying to keep up to date while commuting)".
> >
> > How do you think? IMO, I think discussions on JIRA can be forwarded
> > directly to the mailing list, which is convenient. But indeed sometimes
> we
> > have too many JIRA notifications.
> >
> > Should we stop some JIRA notifications like "closed event" of ISSUE to
> > reduce the notifications?
> >
> > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/March2020
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
>


-- 
Thanks,
Xin

Re: Balance the mailing list and JIRA notification

[Xin Wang]

Nice, thanks Xiangdong for the great work.

- Xin

Xiangdong Huang  于2020年3月7日周六 下午3:17写道：

> Hi all,
>
> I created two tickets to INFRA to improve the experiences.
>
> [1] https://issues.apache.org/jira/browse/INFRA-19936
> [2] https://issues.apache.org/jira/browse/INFRA-19935
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2020年3月6日周五 下午9:35写道：
>
> > Hi all,
> >
> > I get two suggestions from this discussion thread:
> >
> > 1. To reduce the emails, only keep "created" and "commented" event
> > notifications (According to [1], we have "closed" and "Generic Event"
> event
> > notifications now).
> > 2. To make the title more readable, change the template of the subject of
> > the notification email, e.g., from "[JIRA][EVENT TYPE](IOTDB-NUMBER)
> title"
> > to "title [JIRA][EVENT TYPE](IoTDB-NUMBER)". It is possible according to
> > [2].
> >
> > Both two changes require INFRA's help.
> > If there is no dissenting opinion, I can create an issue to INFRA JIRA.
> >
> > If the INFRA can not change the title template, there is another
> solution:
> > a. JIRA sends notifications to a new mailing list; b. a robot subscribes
> > the mailing list and once it receives a new mail, it sends it to dev@
> > mailing list with a better title format.
> >
> > [1]
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/notifications
> > [2]
> >
> https://community.atlassian.com/t5/Jira-questions/Configure-Email-Subject/qaq-p/617839
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Christofer Dutz  于2020年3月6日周五 下午7:54写道：
> >
> >> Hi folks,
> >>
> >> here maybe an example how one of the Jira emails looks like for me in my
> >> inbox:
> >> https://ibb.co/WPJ5V9j
> >>
> >> As you can see, from the title there is almost no information I can get.
> >> So I can't see if I'm interested in reading the content or not.
> >>
> >> Usually my process is to simply delete all Jira emails as I am not
> >> willing
> >> to klick on every email in order to find out what they are about.
> >>
> >> It would be great if we could reduce the title of the jira emails
> >> drastically ...
> >> perhaps even change the order of stuff so I could see more of the title
> >> text,
> >> then perhaps it would make working with these emails better.
> >>
> >> Chris
> >>
> >>
> >> Am 06.03.20, 08:42 schrieb "伍 雄" :
> >>
> >> +1
> >>
> >> > 2020年3月6日 15:28，Julian Feinauer 
> 写道：
> >> >
> >> > +1 from me also!
> >> >
> >> > Am 06.03.20, 04:32 schrieb "Dawei Liu" :
> >> >
> >> >Hi，
> >> >
> >> >+1 for only forwarding Jira creation and comment
> >> >
> >> >I think this is a good thing because chair noticed our work.
> >> >
> >> >Maybe we should put more discussion into email and gradually
> >> reduce the distress caused by automatic generation
> >> >
> >> >
> >> >Thanks
> >> >---
> >> >Dawei Liu
> >> >
> >> >
> >> >
> >> >> 2020年3月6日 上午10:53，Xin Wang  写道：
> >> >>
> >> >> It's a real problem. +1 for only forwarding Jira creation and
> >> comment.
> >> >>
> >> >> - Xin
> >> >>
> >> >> Jialin Qiao  于2020年3月6日周五 上午9:12写道：
> >> >>
> >> >>> Hi,
> >> >>>
> >> >>> +1 for only forwarding Jira creation and comment.
> >> >>>
> >> >>> Stopping forwarding operations like closing issue, linking PR,
> >> assigning
> >> >>> issue...
> >> >>>
> >> >>> Could we simplify the issue report format?
> >> >>>
> >> >>> Like this:
> >> >>>

Re: new committer: Dawei Liu

[Xin Wang]

Congrats Dawei!

- Xin

Jialin Qiao  于2020年3月7日周六 上午10:23写道：

> Hi,
>
>
> The Project Management Committee (PMC) for Apache IoTDB
> has invited Dawei Liu to become a committer and we are pleased
> to announce that he has accepted.
>
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> You could get the write-access of our repository by:
>
>
> (1) Update your github id in: id.apache.org , also an email (anything to
> your apache email will forwart to this email).
> (2) Accept the invitation in github to being a member of the apache group.
> (3) Link your accounts via: git.apache.org (To lighten the third option
> MFA Status, you need to download Google Authenticator (Google 身份验证器) in
> your mobile)
> (4）Sign in github by Google Authenticator
> (5) Clone repository with ssh.
>
>
> Yours,
> The Apache IoTDB PPMC



-- 
Thanks,
Xin

Re: [VOTE] Add Flink Connector Support for TsFile

[Xin Wang]

+1 Thanks for the great job.

- Xin

Xiangdong Huang  于2020年3月12日周四 上午11:44写道：

> Hi,
>
> +1.
>
> Sorry for missing the previous email.
> I have read the design document. This is an exciting feature!
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年3月12日周四 上午10:37写道：
>
> > Hi folks,
> >
> > As we discussed in [1], please vote on the proposal to add Flink
> Connector
> > Support for TsFile, and the corresponding design doc [2].
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > The vote is open for the next 72 hours and passes if at least three +1
> > votes and more +1 votes than -1 votes.
> >
> > Best,
> > Jincheng
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/r6dd6afe4e8e4ca42e3ddfbc80609597788f90b214e7a81788c3b51b3%40%3Cdev.iotdb.apache.org%3E
> > [2]
> >
> >
> https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing
> >
>


-- 
Thanks,
Xin

Re: new committer: Wangminhao Gou

[Xin Wang]

Congrats Wangminhao!

- Xin

Jialin Qiao  于2020年3月16日周一 下午3:48写道：

> Hi,
>
>
> The Project Management Committee (PMC) for Apache IoTDB
> has invited Wangminghao Gou to become a committer and we are pleased
> to announce that he has accepted.
>
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> You could get the write-access of our repository by:
>
>
> (1) Update your github id in: id.apache.org , also an email (anything to
> your apache email will forwart to this email).
> (2) Accept the invitation in github to being a member of the apache group.
> (3) Link your accounts via: git.apache.org (To lighten the third option
> MFA Status, you need to download Google Authenticator (Google 身份验证器) in
> your mobile)
> (4）Sign in github by Google Authenticator
> (5) Clone repository with ssh.
>
>
> Yours,
> The Apache IoTDB PPMC



-- 
Thanks,
Xin

Re: [DISUCSS] a new IoTDB website

[Xin Wang]

Looks nice. +1 on changing to the new.

- Xin

Dawei Liu  于2020年3月20日周五 下午5:25写道：

> Hi，
>
> It looks beautiful, but it still feels like 'scenario' doesn't fit the
> overall design.
>
> Some words at the bottom have no space between left and right,
> and the colors in the picture need to be changed.
>
> In addition, markdown's presentation was too narrow under the
> high-resolution screen.
>
> In general I like it very much
>
> +1 nice
>
> Thanks
> ---
> Dawei Liu
>
>
>
> > 2020年3月20日 下午3:59，伍 雄  写道：
> >
> > +1 nice
> >
> >> 2020年3月20日 14:37，Xiangdong Huang  写道：
> >>
> >> Hi all,
> >>
> >> Several days ago I open a discussion about how to make IoTDB website SEO
> >> (search engine optimized).
> >>
> >> Finally, I find we have to compile the website source code to get a new
> one
> >> which consists of totally static HTMLs. Christofer also gave me many
> helps
> >> about how to compile the source code automatically using Maven.
> >>
> >> The work is on [1], and a contributor, SailingR, builds a proto now. You
> >> can preview it on https://rhh.666love.cn
> >> (Now all pages are static HTMLs.  As this is SailingR's personal server,
> >> the access speed may be not quite fast.)
> >>
> >> We can discuss here or on the JIRA if you have any suggestions.
> >>
> >> [1] https://issues.apache.org/jira/browse/IOTDB-521
> >>
> >> Best,
> >> ---
> >> Xiangdong Huang
> >> School of Software, Tsinghua University
> >>
> >> 黄向东
> >> 清华大学 软件学院
> >
>
>

-- 
Thanks,
Xin

Re: [DISCUSS] wiki document structure

[Xin Wang]

Possible structure:

*Community*
 - how to contribute
 - how to release
 - how to invite new PPMC & Committer (templates for nominating)
 - powered by
 - versioning policy

*Design Documents*

*Ecosystem*
 - official connectors
 - third party projects

*Weekly report*
 - 2020.03.23~2020.03.30


Others could be put on the website.

- Xin

Jialin Qiao  于2020年3月25日周三 下午12:03写道：

> Hi,
>
> Does someone have ideas about this?
>
> Thanks,
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
>
> Jialin Qiao  于2020年3月22日周日 下午8:48写道：
>
> > Hi,
> >
> > > As for the finalized doc, we could just refer to the GitHub repository.
> >
> > +1
> >
> > > There exist many blank pages (for example release history, white paper,
> > resources, …) Should we fill the content?
> >
> > They could be removed.
> >
> > From my side, the wiki acts more like shared notes for developers, so I
> > prefer to make the wiki as simple as possible.
> >
> > I adjust some items:
> >
> > (1) The IoT ecosystem or New TsFile is either user guide or design
> > documents.
> > (2) The paper could be downloaded from the website, so I removed it from
> > the wiki.
> >
> > The folder could be like this:
> >
> >  Design Document
> >   |  Unpublished design doc
> >
> >  Weekly report
> >
> >  Community
> >   |  Email templates for nominating new PPMC & Committer
> >   |  How to release a version
> >   |  How to validate a release candidate
> >
> >  Metting notes (maybe this could be put to the website)
> >
> >  Performance test report (The performance of the released version
> > could be put to the website)
> >   |  Performance test of PR-xxx
> >   |  Performance test of version-xxx
> >
> > Thanks,
> > —
> > Jialin Qiao
> > School of Software, Tsinghua University
> >
> > 乔嘉林
> > 清华大学 软件学院
> >
> >
> > 孙泽嵩  于2020年3月22日周日 下午8:24写道：
> >
> >> Hi Dawei,
> >>
> >> Thanks for your proposal. I totally agree with you. We may maintain some
> >> unpublished design documents which are still under discussion in wiki
> page.
> >> As for the finalized doc, we could just refer to the GitHub repository.
> >>
> >> There exist many blank pages (for example release history, white paper,
> >> resources, …) Should we fill the content? I notice that they are not
> >> mentioned in Dawei’s propose  catalogs.
> >>
> >> Best,
> >> ---
> >> Zesong Sun
> >> School of Software, Tsinghua University
> >>
> >> 孙泽嵩
> >> 清华大学 软件学院
> >>
> >> > 2020年3月22日 15:56，Dawei Liu  写道：
> >> >
> >> > Hi,
> >> >
> >> > The day before yesterday I copy the weekly news into wiki, I found the
> >> document structure is not very clear,
> >> > so want to rearrange the wiki document structure.
> >> >
> >> > I'd like to discuss a few questions before doing that, what a wiki is
> >> for, and what differentiates it from the site (iotdb.apache.org).
> >> >
> >> > My personal opinion is that it is more like a notebook in our growing
> >> up,
> >> > which can publish some notes before we decide,
> >> > such as the design document to new Tsfile, or the test report during
> >> our optimization process, etc.
> >> > which is not suitable for publishing on the official website.
> >> >
> >> > So I organized several hierarchical catalogs:
> >> >
> >> >  Community
> >> >  |  Weekly news
> >> >  |  PPMC & Committer
> >> >  |   …. and more
> >> >
> >> >  IoT ecosystem
> >> >  |  Flink
> >> >  |  MQTT
> >> >
> >> >  Document
> >> >  |  Unpublished design doc
> >> >
> >> >  Metting notes
> >> >  |  
> >> >
> >> >  Parer，feature
> >> >  |  PISA
> >> >  |  New TsFile
> >> >  |  Performance test
> >> >
> >> >  Apache Governance
> >> >  |  how to release a version
> >> >
> >> >
> >> >
> >> >
> >> > Looking forward to your reply
> >> >
> >> >
> >> > Thanks
> >> > ---
> >> > Dawei Liu
> >> >
> >> >
> >>
> >>
>


-- 
Thanks,
Xin

Re: Please have patient to wait for all Travis-CI passed before you merge PRs.

[Xin Wang]

Thanks Xiangdong, good tip for everyone.

- Xin

Xiangdong Huang  于2020年4月8日周三 下午2:36写道：

> Hi,
>
> I notice there were several PRs that did not pass the Travis-CI test but be
> merged...
>
> Maybe some errors can be ignored, but please pay attention to each error
> that Travis-CI reports...
>
> If you really want to merge a PR that is not passed by Travis-CI, please
> leave a message on the PR to let others know. And, I'd like to share a
> screenshot  [1] to you and the sentence: "*You should only continue if you
> are sure of what you are doing*"...
>
> Besides, I think we need to keep the rule that a PR can be merged only
> after at least one Committer approved.
>
> [1]
>
> https://www.howtogeek.com/wp-content/uploads/2013/03/firefox-about-config-warning.png
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>


-- 
Thanks,
Xin

Re: IoTDB supports MQTT protocol now

[Xin Wang]

I'm glad to work with you to make our community better and better, and
bring more value to users.

- Xin

Jialin Qiao  于2020年4月9日周四 上午11:26写道：

> Hi,
>
> Great! Thanks to the contribution of Xin Wang :)
>
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2020年4月9日周四 上午11:22写道：
>
> > Hi,
> >
> > As we know, MQTT protocol is very popular in IoT area.
> > Therefore, I'd like to share the new progress to all of you: Now, IoTDB
> > supports using MQTT protocol to write data directly.
> >
> > Early adopters can try the feature by compiling source code on the master
> > branch of IoTDB.
> > User guide can be found in [1].
> >
> > [1]
> >
> >
> http://iotdb.apache.org/UserGuide/master/4-Client/6-Programming%20-%20MQTT.html
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
>


-- 
Thanks,
Xin

Re: [ANNOUNCE] IoTDB Weekly News (2020-04-03~2020-04-10)

[Xin Wang]

Thanks Dawei, nice work!

- Xin

Xiangdong Huang  于2020年4月10日周五 下午11:44写道：

> Hi,
>
> Thank you, Dawei!
>
> Very glad to see so many new features (especially so many integrations) in
> IoTDB.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Dawei Liu  于2020年4月10日周五 下午11:04写道：
>
> > 大家好，
> >
> > 很开心又一次与大家分享 IoTDB 社区周报。
> >
> > 本周是忙碌的一周，一共合并了 40 多个 PR，涉及7000多行代码修改。
> >
> > 祝周末愉快
> >
> > [一周寄语]
> > 1.所有 PR 合并前记得等一等 Travis-CI 的报告
> > 2.欢迎各位分享自己使用IoTDB的场景，或准备使用IoTDB的场景
> >
> > [本周大事件]
> > 1. TsFile-Flink-Connector 的读取部分已经完成，非常感谢 Wei Zhong.
> >
> > 2. IoTDB 现在支持了 MQTT 协议，你可以直接使用 mqtt 协议入库数据，
> > 感谢 Xin Wang，详情请看：
> > https://github.com/apache/incubator-iotdb/pull/929
> >
> > 3. 现在 IoTDB 可以集成到 OSGI 框架中使用了，非常感谢 etiennerobinet，详情请看：
> > https://github.com/apache/incubator-iotdb/pull/952
> >
> > 4. 马上准备发布 0.9.2，我做为本次 RM 已经准备好了 GPG-Key 和 change list，
> > 请留意之后的投票邮件
> >
> > 5. 感谢 mychaow 修复分布式版本中修复 NodeTool 不能正常使用的问题
> >
> > 6. 分布式版本在开发元数据查询功能和日志持久化，预计下周就可以见到 PR
> >
> > 7. 还支持启动 IoTDB 时指定部分配置，修复了 0.8 到 0.9 的升级 bug，增加大量文档，等等。。
> >
> >
> > Thanks
> > ---
> > Dawei Liu
> >
> >
> >
> > > 2020年4月10日 下午11:02，Dawei Liu  写道：
> > >
> > > Dear community,
> > >
> > >
> > > I am very happy to share with you again the IoTDB weekly news.
> > >
> > > This has been a busy week, merged 40+ PR and 7,000+ code changes.
> > >
> > > Have a good weekend.
> > >
> > > [Best wishes]
> > > 1. Please wait for Travis-CI report before all PR merge
> > > 2. Welcome to share your own scenarios of using IoTDB or preparing to
> > use IoTDB
> > >
> > >
> > > [Big evevnt]
> > > 1. The data source of tsfile-flink-connector has been completed.
> > > Thanks very much to Wei Zhong.
> > >
> > >
> > > 2. Now IoTDB supports the MQTT protocol,
> > > you can directly use the MQTT protocol to warehouse data,
> > > thanks very much to Xin Wang. For details, please see:
> > > https://github.com/apache/incubator-iotdb/pull/929
> > >
> > >
> > > 3. Now IoTDB can be integrated into the OSGI framework.
> > > Thank you very much for etiennerobinet.
> > > https://github.com/apache/incubator-iotdb/pull/952
> > >
> > >
> > > 4. Prepare to release 0.9.2 immediately.
> > > I as the RM, have prepared the the gpg-key and change list.
> > > Keep an eye on the voting mail.
> > >
> > > 5. Thanks to mychaow for fixing a problem with NodeTool not working
> > > properly in the distributed version
> > >
> > >
> > > 6. The distributed version is developing metadata query function and
> log
> > persistence,
> > > and we expect to see PR next week
> > >
> > >
> > > 7. It also supports the specified configuration when starting the
> IoTDB,
> > > fixes the upgrade bug of 0.8 to 0.9, adds a lot of documents, and so
> on.
> > >
> > >
> > >
> > > Thanks
> > > ---
> > > Dawei Liu
> > >
> > >
> >
> >
>


-- 
Thanks,
Xin

Re: priority of Maven Repos (Maven Central and Bintray)

[Xin Wang]

Hi,

The fixing has been included in
https://github.com/apache/incubator-iotdb/pull/1031

- Xin

Willem Jiang  于2020年4月12日周日 上午8:39写道：

> Normally maven use the central repo by default, and it just flow the
> repo definition in the pom to download the jars[1][2].
> If we need to download center jar which is not provided by central
> repo, we could put the repo to submodule pom to avoid this problem.
> BTW,  if we can download the mqtt related jars from central repo, it's
> better we don't add any extra repo in the root pom.
>
> [1]
> https://stackoverflow.com/questions/5325407/how-to-set-order-of-repositories-in-maven-settings-xml/5325685#5325685
> [2]http://maven.apache.org/guides/mini/guide-multiple-repositories.html
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Apr 11, 2020 at 5:53 PM Xiangdong Huang 
> wrote:
> >
> > Hi,
> >
> > In PR #929 [1], we add jcenter.bintary.com as a new maven repo (in root
> > pom.xml) to download a mqtt dependency jar.
> >
> > However, today when I compiled IoTDB source code from a new PC (i.e., my
> > local .m2/repository folder is empty),  I find many dependencies, e.g.,
> > junit, jline, etc., are downloaded from bintray..
> >
> > The terrible thing is, the download speed from the bintray repo is far
> > slower than maven central.. (at least in my network environment).
> >
> > So, does someone know how to define the priority of multiply maven repos?
> >
> > Or, can we move the new maven repo definition to sub modules?
> >
> > [1] https://github.com/apache/incubator-iotdb/pull/929
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
>


-- 
Thanks,
Xin

Re: How about adding an online experience

[Xin Wang]

Good idea. It would be great for new users. Now, we can provide readonly DB
service for the first step.

- Xin

Dawei Liu  于2020年4月12日周日 下午2:07写道：

> Hi,
>
>
> Not supporting write may affect the user's experience,
>
>
> However, if the write function is open, I do not know whether the user
> will illegally write a large amount of data, resulting in a waste of
> resources.
>
>
> Do you have a good suggestions?
>
>
>
>
> Thanks
> ---
> Dawei Liu
>
>
>
> On 04/12/2020 14:01，Xiangdong Huang wrote：
> Hi,
>
> IoTDB supports ReadOnly mode now.
>
> However, is it really fine that the online demo does not support write
> data?
> (tryRedis supports write)
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> Dawei Liu  于2020年4月12日周日 下午1:58写道：
>
> Hi,
>
>
> Yes, maybe we can implement a simple interface in the server model that
> can execute all the queries and return the results
>
>
>
>
>
>
>
>
> Thanks
> ---
> Dawei Liu
>
>
>
> On 04/12/2020 11:24，Jialin Qiao wrote：
> Hi,
>
> Good idea. Maybe we could provide a read-only IoTDB.
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> -原始邮件-
> 发件人: "Dawei Liu" 
> 发送时间: 2020-04-11 22:38:11 (星期六)
> 收件人: "dev@iotdb.apache.org" 
> 抄送:
> 主题: How about adding an online experience
>
> Hi，
>
>
> When I am browsing the Redis website recently, i found an interesting
> feature [1] that allows developers to quickly experience product features
> without having to learn complex compilation, installation, and
> configuration.
>
>
> So I'm thinking about whether we have necessary to launch such a function,
> let the user to read a lot of our user documentation and implementation of
> interactive experience.
>
>
> Do you have any better ideas?
>
>
>
>
> [1] http://try.redis.io/
>
>
>
>
>
>
> Thanks
> ---
> Dawei Liu
>
>
>
>

-- 
Thanks,
Xin

Re: Please ignore the build failure message today.

[Xin Wang]

Good job. Thanks Xiangdong.

- Xin

Xiangdong Huang  于2020年4月13日周一 下午5:41写道：

> Hi all,
>
> I am trying to update some settings of Jenkins (to let code quality stage
> skip the "website" module).
>
> Before finished, there may be several build failure messages. You can
> ignore them.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>


-- 
Thanks,
Xin

Re: Support limit&offset in show timeseries

[Xin Wang]

Good work! This is very useful when the query result is large.

- Xin

Jialin Qiao  于2020年4月22日周三 下午2:55写道：

> Hi,
>
>
> Show timeseries may produce large result set, it's better to support
> limit&offset for iteration.
>
> I submit a PR [1] for this.
>
>
> [1] https://github.com/apache/incubator-iotdb/pull/1085
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院



-- 
Thanks,
Xin

Re: hello iotdb community

[Xin Wang]

Welcome Xinfeng to the IoTDB community!
Here is a guide for contributing.
https://iotdb.apache.org/Development/ContributeGuide.html

- Xin

Dawei Liu  于2020年5月11日周一 上午11:06写道：

> Hi Xinfeng，
>
>
> Welcome.
> I hope you can learn about iotdb as soon as possible and use it in
> combination with the company's business.
> Don't hesitate to contact me if you encounter any problems in the use.
> Looking forward to your further contribution.
>
>
> Thanks
> -
> Dawei Liu
>
>
>
>
> On 05/11/2020 10:38，王欣峰<18519707...@163.com> wrote：
>
>
> Hi Iotdb developers,
>
>
> I am XinFeng Wang, from company uniev Technology Co., Ltd., the company is
> doing business related to charging piles. After listening to the sharing of
> Dawei Liu, I am very interested in iotdb and hope to have the opportunity
> to contribute
>
>
> Cheers,
> XinFeng Wang
> | |
> 王欣峰
> |
> |
> 18519707...@163.com
> |
> 签名由网易邮箱大师定制
>
>

-- 
Thanks,
Xin

Re: [ANNOUNCE] Add Jincheng Sun as a new PPMC of IoTDB

[Xin Wang]

Congrats Jincheng!



Dawei Liu  于2020年5月12日周二 下午4:37写道：

>
>
> wow，Congratulations.
>
>
>
>
> Thanks
> 
> Dawei Liu
> On 05/12/2020 16:32，Wei Zhong wrote：
> Congratulations, Jincheng!
>
> Best,
> Wei
>
> 在 2020年5月12日，15:56，Xiangdong Huang  写道：
>
> Hi all,
>
> I am pleased to announce that after discussion and vote among PPMC groups,
> and publicity on IPMC mailing list, Jincheng Sun is nominated as a new PPMC
> of IoTDB.
>
> Jincheng Sun has joined the IoTDB community for more than 6 months and is
> always active in the mailing list.
>
> Benefit from his experience of being a Flink PMC (and Apache Member
> recently), he pointed out many mistakes in IoTDB's documents/website and
> devoted himself to integrate IoTDB with Apache Flink.
>
> Jincheng Sun knows Apache way well and has rich experience working on large
> projects (e.g., Flink), we look forward to his contribution in the future.
>
> Now we have 24 PPMC totally, which come from Tsinghua University,
> PragmaticMinds, Alibaba, Microsoft, K2Data, ByteDance, Tencent and NELBDS.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>


-- 
Thanks,
Xin

[DISCUSS] Move connectors to separate directories

[Xin Wang]

Hi devs,

Currently, IoTDB provides a lot of built-in connectors. For better
management, how about putting these connectors in a/some separate
directory(s)
(maybe `connectors`, or
`iotdb-connectors/tsfile-connectors/other-connectors`).

Look forward to your reply.


Current connectors:
  - iotdb connectors: spark, flink
  - tsfile connectors: hadoop, hive, spark, flink
  - other connectors: grafana, calcite


-- 
Thanks,
Xin

Re: new committer:Yuyuan Kang

[Xin Wang]

Congrats Yuyuan!



Jialin Qiao 于2020年5月14日 周四09:18写道：

> Hi,
>
>
> The Project Management Committee (PMC) for Apache IoTDB
> has invited Yuyuan Kang to become a committer and we are pleased
> to announce that he has accepted.
>
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> You could get the write-access of our repository by:
>
>
> (1) Update your github id in: id.apache.org , also an email (anything to
> your apache email will forwart to this email).
> (2) Accept the invitation in github to being a member of the apache group.
> (3) Link your accounts via: git.apache.org (To lighten the third option
> MFA Status, you need to download Google Authenticator (Google 身份验证器) in
> your mobile)
> (4）Sign in github by Google Authenticator
> (5) Clone repository with ssh.
>
>
> Yours,
> The Apache IoTDB PPMC

-- 
Thanks,
Xin

Re: [DISCUSSION] IoTDB Online Community Meetup

[Xin Wang]

Thanks Julian for your good idea.
I'm +1 on both since we have both chinese and english users/contributors .
Other projects like Flink have similar meetups(some chinese topics and some
english topics).



Julian Feinauer  于2020年5月14日周四 下午5:00写道：

> Hi folks,
>
> as discussed in the other thread I want to start a discussion here.
> I would love to have a online meetup with all of you guys and it would
> surely also interetsting for all the „newer“ contributors, comitters and
> PPMCs we have.
> As the community is pretty Chinese-centered at the moment I would like to
> hear your opinions on whether you would prefer a meetup in Chinese first
> hand or if everybody feels fluent enough to do it in english.
> Of course I would prefer english but if many people do not feel
> „comfortable“ and do not properly understand things then Chinese is better
> fort he commuity.
> Or we do both.
>
> What are your thoughts? Chinese Meetup, English Meetup, Both?
>
> Julian
>


-- 
Thanks,
Xin

Re: About Cluster

[Xin Wang]

Hi Xiangdong,

The attach is not available.

Xiangdong Huang  于2020年6月3日周三 下午1:12写道：

> Hi,
>
> As far as I know, development is almost done. All codes are on the
> `cluster_new` branch.
>
> But the Travis tests fail on the branch now. So, more time for testing is
> needed.
>
> The design follows a Chinese document [1], but the English design document
> is not done.
>
> [1] Apache IoTDB 的分布式框架设计.pdf
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> TianFeng  于2020年6月3日周三 上午10:14写道：
>
> > Hi all
> >
> >
> >     I am interested in cluster mode of the IoTDB.I'm curious
> how
> > is it going?
> >
> >
> > Best Regards!
>


-- 
Thanks,
Xin

Re: About Cluster

[Xin Wang]

Thanks Jack!

@Xiangdong We can put the design docs on IoTDB website.


Jack Tsai  于2020年6月4日周四 上午5:08写道：

> Hi Xin,
>
>
>
> I had also begun to study the knowledge of of IoTDB about this part. I
> think the document what Xiangdong attached in mail could be found here [1].
>
>
>
> [1] http://scis.scichina.com/cn/2020/SSI-2019-0189.pdf
>
>
>
> Best,
>
> Jack Tsai
>
>
> 寄件者: Xin Wang<mailto:data.xinw...@gmail.com>
> 傳送時間: 2020年6月3日 上午 09:44
> 收件者: dev@iotdb.apache.org<mailto:dev@iotdb.apache.org>
> 主旨: Re: About Cluster
>
> Hi Xiangdong,
>
> The attach is not available.
>
> Xiangdong Huang  于2020年6月3日周三 下午1:12写道：
>
> > Hi,
> >
> > As far as I know, development is almost done. All codes are on the
> > `cluster_new` branch.
> >
> > But the Travis tests fail on the branch now. So, more time for testing is
> > needed.
> >
> > The design follows a Chinese document [1], but the English design
> document
> > is not done.
> >
> > [1] Apache IoTDB 的分布式框架设计.pdf
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > TianFeng  于2020年6月3日周三 上午10:14写道：
> >
> > > Hi all
> > >
> > >
> > >     I am interested in cluster mode of the IoTDB.I'm curious
> > how
> > > is it going?
> > >
> > >
> > > Best Regards!
> >
>
>
> --
> Thanks,
> Xin
>
>

-- 
Thanks,
Xin

Re: [DISCUSS] graduation process: Charter and VP of IoTDB discussion

[Xin Wang]

+1 for the charter and Xiangdong as VP.

Xiangdong Huang  于2020年9月1日周二 下午4:34写道：

> Hi Dawei,
>
> > ‘management' and ‘analysis' makes me feel too broad.
>
> That is why we need to discuss the project's description.
>
> Users may do not want to store data simply, but also use the data.
>
> "management" means storage and query.
> We are trying to provide diverse and powerful query functions to users.
> So, just "storage" can not cover the goal of the project.
>
> Besides, one trend in DB domain is letting database supporting more
> analytics/processing.
>
> For example, in IIoT, queries like downsampling, analysis like FFT,
> calculating something across two or more time series are useful.
>
> Moving-window in UDF, and forward data according to some rule when loading
> data in realtime are also useful.
>
> We will support that soon or later, right?
>
> That's why I'd like to reserve the word "analysis".
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Dawei Liu  于2020年9月1日周二 下午4:13写道：
>
> > Hi，
> >
> >
> > Big +1 for Xiangdong as VP.
> >
> >
> > > So, how about:  "an IoT native database with high performance for data
> > > management and analysis, on the edge and the cloud."
> >
> >
> > ‘management' and ‘analysis' makes me feel too broad.
> > So, how about:  "an IoT native database with high performance for data
> > storage, on the edge and the cloud.”
> >
> >
> > Best,
> > Dawei
> >
> >
> >
> >
> > On 09/1/2020 15:57，Xiangdong Huang wrote：
> > Hi,
> >
> > As for the description of the project, the "native database" is awkward.
> >
> > It should be "IoT native database"
> >
> > So, how about:  "an IoT native database with high performance for data
> > management and analysis, on the edge and the cloud."
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
> >
> >
> > runhus...@foxmail.com  于2020年9月1日周二 下午3:43写道：
> >
> > Hi,
> > Big +1 for the charter and Xiangdong as VP!
> >
> >
> >
> > Thanks.
> >
> > Chao Wang
> > BONC Ltd
> >
> >
> > From: Xiangdong Huang
> > Date: 2020-09-01 15:26
> > To: dev
> > Subject: Re: [DISCUSS] graduation process: Charter and VP of IoTDB
> > discussion
> > Hi,
> >
> > Thanks, runhuster (better to leave a signature in the tail of your email
> > :D), I like your suggestion.
> >
> > Thanks, Julian and Jialin. It is my honor. :D
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
> >
> >
> > Jialin Qiao  于2020年9月1日周二 下午3:24写道：
> >
> > Hi,
> >
> > +1 for the charter and Xiangdong as VP!
> >
> > Thanks,
> > --
> > Jialin Qiao
> > School of Software, Tsinghua University
> >
> > 乔嘉林
> > 清华大学 软件学院
> >
> > -原始邮件-
> > 发件人: "Julian Feinauer" 
> > 发送时间: 2020-09-01 13:55:15 (星期二)
> > 收件人: "dev@iotdb.apache.org" , "Christofer Dutz"
> > <
> > christofer.d...@c-ware.de>
> > 抄送:
> > 主题: Re: [DISCUSS] graduation process: Charter and VP of IoTDB
> > discussion
> >
> > Hi,
> >
> > thanks for bringing that up.
> > Indeed I think your short proposal is right.
> >
> > Rergarding the VP, I had a short off-list discussion with @Christofer
> > Dutz and we both agreed that it should be someone who speaks Chinese and
> > English as our community is kind of bilingual.
> >
> > Regarding the amount of work and support that Xiangdong put into the
> > community development and also his work in translating between English
> > and
> > Chinese community parts (his English is pretty good, I hope his Chinese
> > too^^) I like to suggest Xiangdong, as first VP of IoTDB.
> >
> > What do others think about that?
> >
> > Julian
> >
> > Am 01.09.20, 06:17 schrieb "Xiangdong Huang" :
> >
> > Hi,
> >
> > The vote for start the graduation process has last two days and we
> > have
> > received many +1.
> >
> > According to [1], we can begin to discuss the charter (resolution)
> > in
> > parallel.
> >
> > The main task is using one or two sentences to define what IoTDB
> > is:
> >
> > A good resolution is neither too narrow nor too broad. If the
> > project’s
> > scope is too narrow, then its activities will be unnecessarily
> > constrained.
> > If a project’s scope is too broad then it may lack focus and suffer
> > from
> > governance issues.
> >
> > Besides, we need also to elect someone as the VP of the project.
> >
> > So, any ideas?
> >
> > IMO, how about:
> >
> > Apache IoTDB: a native database for storing and analyzing Internet
> > of
> > Things data, on the edge and the cloud.
> >
> > [1]
> >
> >
> >
> https://incubator.apache.org/guides/graduation.html#the_graduation_process
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
> >
> >
> >
> >
>


-- 
Thanks,
Xin

Re: [NEWS] The largest PR (in 2020) is merged

[Xin Wang]

Great news!

王超  于2020年12月9日周三 上午10:46写道：

> Congratulation!
>
>
> I like Jialin's finger which clicked the button.
>
>
> Good job!
>
>
> | |
> Chao Wang
> |
> |
> BONC, Ltd
> ccgow...@163.com
> |
> 签名由网易邮箱大师定制
> On 12/9/2020 10:26，谭新宇 wrote：
> Hi,
>
>
> What an exciting moment! Hope the cluster module can be more stable and
> efficient under our effort!
>
>
> Best
> --
> XinYu Tan



-- 
Thanks,
Xin

Re: New committers: Xiangwei Wei and Jesse Zhou

[Xin Wang]

Congrats Xiangwei and Jesse!!

Mark Liu  于2021年2月22日周一 上午9:16写道：

> Congratulations, Xiangwei and Jesse
>
> Best,
> ---
> Mark Liu
>
> 田原  于2021年2月22日周一 上午9:07写道：
>
> > Xiangwei, Jesse,
> >
> > Congratulations!
> >
> >
> > Best,
> > ---
> > Yuan Tian
> >
> >
> >
> > > -原始邮件-
> > > 发件人: "Jialin Qiao" 
> > > 发送时间: 2021-02-20 18:36:13 (星期六)
> > > 收件人: dev@iotdb.apache.org
> > > 抄送:
> > > 主题: New committers: Xiangwei Wei and Jesse Zhou
> > >
> > > Hi,
> > >
> > >
> > > The Project Management Committee (PMC) for Apache IoTDB has invited
> > Xiangwei Wei and Jesse Zhou
> > > to become committers and we are pleased to announce that they have
> > accepted.
> > >
> > >
> > > Being a committer enables easier contribution to the project since
> > there is no need to go via the patch
> > > submission process. This should enable better productivity.
> > > Being a PMC member enables assistance with the management and to
> > guide the direction of the project.
> > >
> > >
> > > You could get the write-access of our repository by:
> > >
> > >
> > > (1) Update your github id in: id.apache.org , also an email
> > (anything to your apache email will forwart to this email).
> > > (2) Accept the invitation in github to being a member of the apache
> > group.
> > > (3) Link your accounts via: git.apache.org (To lighten the third
> > option MFA Status, you need to download Google Authenticator (Google
> 身份验证器)
> > in your mobile)
> > > (4) Sign in github by Google Authenticator
> > > (5) Clone repository with ssh.
> > >
> > >
> > > Welcome Xiangwei and Jesse!
> > >
> > >
> > > Yours,
> > > The Apache IoTDB PMC
> > 
>


-- 
Thanks,
Xin

Re: new PMC: Chao Wang

[Xin Wang]

Congrats Chao!

Zhou Yifu  于2022年12月15日周四 17:19写道：

> Congrats! Well-deserved!
>
> Thanks,
> Yifu Zhou
>
> 获取 Outlook for iOS
> 
> 发件人: Jialin Qiao 
> 发送时间: Thursday, December 15, 2022 2:56:44 PM
> 收件人: dev@iotdb.apache.org 
> 主题: new PMC: Chao Wang
>
> Hi,
>
> The Project Management Committee (PMC) for Apache IoTDB
> has invited Chao Wang to become a PMC and we are pleased
> to announce that he has accepted.
>
> Welcome, Chao Wang!
>
> Yours,
> The Apache IoTDB PMC
>


-- 
Thanks,
Xin

Re: new committer: Rongzhao Chen

[Xin Wang]

Congrats Rongzhao!

Houliang Qi  于2023年1月4日周三 18:10写道：

> Congratulations！
> ConfigNode is the brain of the cluster, Rongzhao make a great contribution
> to ConfigNode.
> Hope to see more useful functions contributed by Rongzhao!
>
>
> Thanks,
> ---
> Houliang Qi
> BONC, Ltd
>  Replied Message 
> | From | Eric Pai |
> | Date | 01/4/2023 17:15 |
> | To | dev@iotdb.apache.org |
> | Subject | 答复: new committer: Rongzhao Chen |
> 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.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> You could get the write-access of our repository by:
>
> (1) Update your github id in: id.apache.org , also an email (anything
> to your apache email will forward to this email).
> (2) Accept the invitation in github to be a member of the apache group.
> (3) Link your accounts via: git.apache.org (To lighten the third
> option MFA Status, you need to download Google Authenticator (Google
> 身份验证器) in your mobile)
> (4）Sign in github by Google Authenticator
> (5) Clone repository with ssh.
>
> Welcome, Yongzao!
>
> Yours,
> The Apache IoTDB PMC
>


-- 
Thanks,
Xin

Re: [discuss] consider revert the feature of multi-tenancy

[Xin Wang]

Hi guys,


Here is a suggestion. If a change is identified as a large or controversial
change. It might require an Improvement Proposal(refer to FLIP*1), and a
discussion on the dev mailing list to reach agreement and consensus.


1*
https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals

Houliang Qi  于2023年4月12日周三 21:30写道：

> A healthy community requires different voices. It is these different
> voices that enable us to strictly review each feature and consider each
> scenario more comprehensively, so that we can better provide users with
> better features.
>
> I am also very grateful to the colleagues who participated in this
> discussion.
>
> If it is still the previous discussion point, I will stick to my previous
> opinion and will not reply again.
>
> If someone brings up a new discussion point, I think it is possible to
> open another discussion.
>
>
>
>
>
> Thanks.
> ---
> Houliang Qi
> BONC, Ltd
>
>
>  Replied Message 
> | From | Houliang Qi |
> | Date | 04/12/2023 20:08 |
> | To | dev@iotdb.apache.org |
> | Subject | Re: [discuss] consider revert the feature of multi-tenancy |
> Hi,
> I would like to end by stating my point of view. And I don't want to say
> it a second time.
>
> First of all, I agree to change the name of this feature to resource
> control. The reason why I think that both multi-tenancy and
> resource-control are suitable for us is that what we are currently doing is
> to limit the functions of users or databases resources.
>
>
> @Jinrui 2. A true multi-tenant system should also have features such as
> per-tenant configurations, customized tenant roles and permissions, and
> clear separation of tenant data.
> @Jinrui 3. In our case, the lack of configuration file isolation in the
> current implementation means that different tenants may inadvertently
> affect each other's configurations, which goes against the core principle
> of multi-tenancy. The example I raised in last mail is also used to
> illustrate it rather than the function scope definition.
>
>
>
> But I disagree with Jinrui said above:
>
> You can refer to this paper [1]. This document summarizes multi-tenancy
> very well. First of all, it does not mean that multi-tenancy must have the
> ability to configure isolation. For this feature, we do share
> configuration, but our data is logically isolated and can limit some
> resources such as cpu, memory, timeseries, etc. This is also a way to
> realize multi-tenancy. Of course, each tenant can even use a different
> operating system, which is also a way to realize multi-tenancy. Please
> don't limit the way to realize multi-tenancy. There I would like to paste a
> passage from the paper as a conclusion:
>
>
> By sharing infrastructure, middleware, or application among tenants,
> multi-tenancy can be achieved
>
> In a multi-tenant architecture, a single instance of the software is
> deployed on the server functioning on the service provider infrastructure.
> It provides access to multiple tenants at the same time, as describe by
> Karataş et al. [KCD+17]. Abdul et al. [ABG+18]describe several multi-tenant
> data layer models, such as dedicated, isolated, shared, and hybrid. By
> sharing infrastructure, middleware, or application among tenants,
> multi-tenancy can be achieved. Figure 2.2 visualizes the multi-tenancy
> strategies described by Walraven et al. [WLJ14]. However, application-level
> multi-tenancy with a shared everything architecture can lead to cost
> reduction. Chong et al. [CCW06] have outlined several viable database
> patterns, primarily for Microsoft SQL Server, which supports
> application-level multi-tenancy. In a multi-tenant situation, they present
> three major strategies which are: distinct databases, shared databases with
> distinct schemes, and shared databases with shared schemes.
>
> [1] Enabling multi-tenant scalable IoT platforms.
> https://elib.uni-stuttgart.de/bitstream/11682/11024/1/Enabling%20multi-tenant%20scalable%20IoT%20platforms.pdf
>
>
>
>
>
> Thanks,
> ---
> Houliang Qi
> BONC, Ltd
>
>
>  Replied Message 
> | From | Jinrui 张金瑞<329920...@qq.com.INVALID> |
> | Date | 04/12/2023 19:14 |
> | To |  |
> | Subject | Re: [discuss] consider revert the feature of multi-tenancy |
> Hi,
>
> Perhaps I need to emphasize again that regarding the multi-tenancy section
> discussed, the following is my conclusion:
> 1. The implementation of the PR cannot be called multi-tenancy
> 2. Multi-tenancy is not equal to resource control.
>
> The reasons are:
> 1. While resource isolation or control can be used to enable
> multi-tenancy, it's not the only requirement.
> 2. A true multi-tenant system should also have features such as per-tenant
> configurations, customized tenant roles and permissions, and clear
> separation of tenant data.
> 3. In our case, the lack of configuration file isolation in the current
> implementation means that different 

[jira] [Created] (IOTDB-484) Added maven status badge

[Xin Wang (Jira)]

Xin Wang created IOTDB-484:
--

 Summary: Added maven status badge
 Key: IOTDB-484
 URL: https://issues.apache.org/jira/browse/IOTDB-484
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Document
Reporter: Xin Wang


Added maven status badge for tracking latest jar version and linking to maven 
central repo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-485) Fix the broken link for `Client/Shell tools`

[Xin Wang (Jira)]

Xin Wang created IOTDB-485:
--

 Summary: Fix the broken link for `Client/Shell tools`
 Key: IOTDB-485
 URL: https://issues.apache.org/jira/browse/IOTDB-485
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Document
Reporter: Xin Wang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-486) Correct typo and broken link in `example/ rocketmq/readme.md`

[Xin Wang (Jira)]

Xin Wang created IOTDB-486:
--

 Summary: Correct typo and broken link in `example/ 
rocketmq/readme.md`
 Key: IOTDB-486
 URL: https://issues.apache.org/jira/browse/IOTDB-486
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Document
Reporter: Xin Wang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-488) Static members shouldn't be accessed through class instances

[Xin Wang (Jira)]

Xin Wang created IOTDB-488:
--

 Summary: Static members shouldn't be accessed through class 
instances
 Key: IOTDB-488
 URL: https://issues.apache.org/jira/browse/IOTDB-488
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/Engine
Reporter: Xin Wang


Static members shouldn't be accessed through class instances in

_org.apache.iotdb.db.qp.strategy.PhysicalGenerator_

 

Before:

_Path concatPath = filterPath.addPrefixPath(filterPath, prefix);_

After:

_Path concatPath = Path.addPrefixPath(filterPath, prefix);_

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-489) Variable url pattern should be defined as a constant

[Xin Wang (Jira)]

Xin Wang created IOTDB-489:
--

 Summary: Variable url pattern should be defined as a constant
 Key: IOTDB-489
 URL: https://issues.apache.org/jira/browse/IOTDB-489
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/Engine
Reporter: Xin Wang


Variable url pattern should be defined as a constant 
in`org.apache.iotdb.jdbc.Utils`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IOTDB-484) Added maven status badge

[Xin Wang (Jira)]

[ 
https://issues.apache.org/jira/browse/IOTDB-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037465#comment-17037465
 ] 

Xin Wang commented on IOTDB-484:


[~hxd] Good.

> Added maven status badge
> 
>
> Key: IOTDB-484
> URL: https://issues.apache.org/jira/browse/IOTDB-484
> Project: Apache IoTDB
>  Issue Type: Improvement
>  Components: Document
>Reporter: Xin Wang
>Priority: Minor
>
> Added maven status badge for tracking latest jar version and linking to maven 
> central repo.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-491) Constant name `pool ` should be all uppercase

[Xin Wang (Jira)]

Xin Wang created IOTDB-491:
--

 Summary: Constant  name `pool ` should be all uppercase
 Key: IOTDB-491
 URL: https://issues.apache.org/jira/browse/IOTDB-491
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/Engine
Reporter: Xin Wang


Constant name `pool ` should be all uppercase in 
`org.apache.iotdb.db.query.dataset.NewEngineDataSetWithoutValueFilter`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IOTDB-491) Constant name `pool ` should be all uppercase

[Xin Wang (Jira)]

[ 
https://issues.apache.org/jira/browse/IOTDB-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037535#comment-17037535
 ] 

Xin Wang commented on IOTDB-491:


[~hxd] Got it. thx~

> Constant  name `pool ` should be all uppercase
> --
>
> Key: IOTDB-491
> URL: https://issues.apache.org/jira/browse/IOTDB-491
> Project: Apache IoTDB
>  Issue Type: Improvement
>  Components: Core/Engine
>Reporter: Xin Wang
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Constant name `pool ` should be all uppercase in 
> `org.apache.iotdb.db.query.dataset.NewEngineDataSetWithoutValueFilter`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-492) Remove unused field from hadoop example

[Xin Wang (Jira)]

Xin Wang created IOTDB-492:
--

 Summary: Remove unused field from hadoop example
 Key: IOTDB-492
 URL: https://issues.apache.org/jira/browse/IOTDB-492
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Examples
Reporter: Xin Wang


Remove unused field from hadoop example in 
`org.apache.iotdb.hadoop.tsfile.TSFMRReadExample`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-493) Remove author tags from source code

[Xin Wang (Jira)]

Xin Wang created IOTDB-493:
--

 Summary: Remove author tags from source code
 Key: IOTDB-493
 URL: https://issues.apache.org/jira/browse/IOTDB-493
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/Others
Reporter: Xin Wang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-497) Apache Flink Connector Support

[Xin Wang (Jira)]

Xin Wang created IOTDB-497:
--

 Summary: Apache Flink Connector Support
 Key: IOTDB-497
 URL: https://issues.apache.org/jira/browse/IOTDB-497
 Project: Apache IoTDB
  Issue Type: New Feature
  Components: Core/Others
Reporter: Xin Wang
Assignee: Xin Wang


We all know that Apache Flink is one of the most popular stream computing 
engine, which is widely used in IOT scenes.

This module is the IoTDB integration for Apache Flink, including the IoTDB sink 
that allows a Flink job to write events into timeseries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-502) NPE bug in `org.apache.iotdb.db.service.TSServiceImpl`

[Xin Wang (Jira)]

Xin Wang created IOTDB-502:
--

 Summary: NPE bug in `org.apache.iotdb.db.service.TSServiceImpl`
 Key: IOTDB-502
 URL: https://issues.apache.org/jira/browse/IOTDB-502
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Core/Engine
Reporter: Xin Wang
Assignee: Xin Wang


The IoTDB server throws the following error when accessing 0.10 server(master) 
by 0.9 shell client (latest release).

Exception trace:
{quote}org.apache.iotdb.db.service.TSServiceImpl#getTimeZone
java.lang.NullPointerException: null at 
org.apache.iotdb.db.service.TSServiceImpl.getTimeZone(TSServiceImpl.java:1120) 
at 
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$getTimeZone.getResult(TSIService.java:1853)
 at 
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$getTimeZone.getResult(TSIService.java:1833)
 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at 
org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38) at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:313)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
at java.lang.Thread.run(Thread.java:748)
{quote}
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-503) add checkTimeseriesExists for session

[Xin Wang (Jira)]

Xin Wang created IOTDB-503:
--

 Summary: add checkTimeseriesExists for session
 Key: IOTDB-503
 URL: https://issues.apache.org/jira/browse/IOTDB-503
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/Engine
Reporter: Xin Wang


In most scenarios, we should check whether it already exists before creating, 
otherwise the following exception may be thrown from server:

 
{quote}org.apache.iotdb.db.exception.query.QueryProcessException: Timeseries 
[root.sg.d1.s1] already 
existorg.apache.iotdb.db.exception.query.QueryProcessException: Timeseries 
[root.sg.d1.s1] already exist at 
org.apache.iotdb.db.qp.executor.QueryProcessExecutor.createTimeSeries(QueryProcessExecutor.java:552)
 at 
org.apache.iotdb.db.qp.executor.QueryProcessExecutor.processNonQuery(QueryProcessExecutor.java:122)
 at 
org.apache.iotdb.db.service.TSServiceImpl.executeNonQuery(TSServiceImpl.java:1044)
 at 
org.apache.iotdb.db.service.TSServiceImpl.executePlan(TSServiceImpl.java:1387) 
at 
org.apache.iotdb.db.service.TSServiceImpl.createTimeseries(TSServiceImpl.java:1342)
 at 
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$createTimeseries.getResult(TSIService.java:1953)
 at 
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$createTimeseries.getResult(TSIService.java:1933)
 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at 
org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38) at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:313)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
at java.lang.Thread.run(Thread.java:748)
{quote}
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-506) Compatibility error: The 0.9 server throws exception when accessed by 0.10 session client.

[Xin Wang (Jira)]

Xin Wang created IOTDB-506:
--

 Summary: Compatibility error: The 0.9 server throws exception when 
accessed by 0.10 session client.
 Key: IOTDB-506
 URL: https://issues.apache.org/jira/browse/IOTDB-506
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Core/Engine
Reporter: Xin Wang


The 0.9 server throws exception when accessed by 0.10 session client.
{quote}serverjava.lang.IllegalArgumentException: Path parameter is null at 
org.apache.iotdb.tsfile.read.common.Path.(Path.java:48) at 
org.apache.iotdb.db.service.TSServiceImpl.setStorageGroup(TSServiceImpl.java:1290)
 at 
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$setStorageGroup.getResult(TSIService.java:1725)
 at 
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$setStorageGroup.getResult(TSIService.java:1710)
 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) at 
org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
at java.lang.Thread.run(Thread.java:748)
{quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IOTDB-547) Fix typo for tsfile schema

[Xin Wang (Jira)]

Xin Wang created IOTDB-547:
--

 Summary: Fix typo for tsfile schema
 Key: IOTDB-547
 URL: https://issues.apache.org/jira/browse/IOTDB-547
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/TsFile
Reporter: Xin Wang
Assignee: Xin Wang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)