Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Feb 21st, 2021, Sunday.

Host: Yuan Tian

Online Meeting (Tencent Meeting):

Link:https://meeting.tencent.com/s/1mMNkx54Ejra

meeting room ID: 690 200 054

password: 0221


Time: 2021-02-21 9:00 PM Beijing Time

Host: Yuan Tian


Agenda

Status Updates 

Announce

Apache IoTDB 0.11.3 and 0.12.0 is still in progress



Improvement

#2596 Improve the flush pipeline

We used PublicBAOS(which extends ByteArrayOutputStream in java) as container to hold the encoded data. Encoding task call the write method to put data into it and IO task call the read method to read data from it, persist it to disk.

However, the methods we called in ByteArrayOutputStream are mostly synchronized. Although we won't call the method of the same object simultaneously in the stage of encoding and io, the Biased locking(which is added as a feature after JDK1.6 and is announced to be deprecated in JDK15) will cause the encoding stage to be influenced by the io stage.

The detailed analysis and experiments can be seen in confluence(https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173085039&preview=/173085039/173085040/Pipeline%E5%88%86%E6%9E%90.pdf)


#2629 [Github Issue 2624, 2625] Avoid OOM if user don't close Statement and Session manually

When reusing IoTDBStatement to do queries. The Set in statementId2QueryId is never removed unless the statment is clsoed.

This will cause OOM if using a Statement is used for too long time.


 

#2658 Enhancement: add backgroup exec for cli -e function

Previously, there were some problems while we use the following command to execute in background. Now, we can successfully use it.

nohup ./start-cli.sh -e



#2684 Improve the quality and efficiency of code formatting

The Spotless with google-java-format now in effect.

Notice:

This change touched most of single java file in the repository(70K+). So

most of PRs will require a rebase, follow the steps below:

1. git checkout YOUR_PR

2. git cherry-pick b1261ecb5893ee0d357fec311b4d92ff9039a989

3. mvn spotless:check

4. mvn spotless:apply

5. git add .

6. git commit -m 'Apply Spotless'

# asf git@github.com:apache/iotdb.git (fetch)

# Pull the latest master branch

7. git checkout -b asf_master asf/master

8. git checkout YOUR_PR

9. git rebase asf_master

# Resolve your conflict:

# NOTE: `Accept Yours` for your PR involves files, and `accept Theirs` for

other files.

10 git rebase --continue

# Double check

11. mvn spotless:check

# If you see "build success" successfully, it is proved that rebase has

been successful.

12. mvn clean package -DskipTests

# If you see "build success" successfully, you can push your changes to you

PR branch.


Open Floor 

new ideas, feedback, suggestions.

[Discussion] Monthly Contributor Award

Goal: Keep community more vibrant and attract new contributors

Attention: Not really an award, just a title that we can recognize with an announcement on the official wechat account

Preliminary measure:

  • Amount of PR and reviews on GitHub(codes amount)
  • Activity on mailinglists
  • Contributions(publicity, tutorial, etc.) on social media (e.g. WeChat official account, CSDN, Stack Overflow)
  • Being a conference host or event organizer will also count.


The final equation would be S=0.9Z(code)+0.1Z(mail)

两个方向上的称号:

代码贡献+代码review贡献

[Discussion] Community Mentors

  • Call for mentors and plans
  • Q & A docs(使用 Github issue 维护,所有小组共享)
  • start up docs (导师提供的上手基础资料,如代码仓库、设计文档、如何调、经验分享、公众号等,导师之间可以共享) —— 组建小组群之前
  • Wechat group
  • Phase Feedback(阶段性反馈)


Sign up : 45 people

  • To be as commiter : 17
  • Users needing professional help : 5
  • Both : 23


报名人群可以细分:已经熟悉IoTDB但是对于设计不够熟悉,如何入手修改

感兴趣的模块:查询 / 存储 / 分布式 / 实时计算 / 全部


灵活、不限时间,没有集中的开发时间,与现有社区的committer建立联系

每个导师负责 1-3 人,作为小组


2月10日之前:建群,start up文档,找导师


Proposal] Hackthon (April)

开issue:大家罗列一些想法

https://github.com/apache/iotdb/issues/2715

1 committer + 3 non-committer

面向人群:校内学生+社区贡献者

奖励:现金奖励形式

流程:

报名(3月下旬)

提前1个月确定导师与学生,一个月内可以进行线上沟通交流与设计(4月份)

两三天的集中code时间(5月初)

奖励评定(code结束后)

New Committers公众号推送

祥威、禹任 采访


9th Meeting Schedule

Time: 2021-03-07

Host: Kaifeng Xue



Meeting bi-weekly Sunday at 9:00 pm Beijing Time.

...

  1. About meet up
    We held the first Apache IoTDB offline meetup successfully in 29 November. We mainly talked about the experience of using IoTDB and the development of it. But as it's the first time, we have many aspects to improve.

    1. Add free talk
      In last meetup, the main activities we held were the lectures about IoTDB using and developing. We got a lot from these lectures. But the offline meetup is also a good chance to help community members get to know each other. So I think, we can add free talk in meetup, maybe academic or not, to offer this chance.

    2. Bring the summary of meetup back to community
      For various reasons, some friends in the community can't join meetup offline. Therefore, we need to record the meetup by video and doc, and share the summary of meetup to them by mailing list or IoTDB website.

  2. Community gift
    We plan to design some community themed little gifts for contributors who has contributions (code, doc or something else) to the community. At present, we have completed the design of mouse pad. Next, we can collect the personal information of the contributors to mail these gifts.

    Image Modified

  3.    Call for community mentors
    We used to propagate IoTDB in many Chinese universities, and many students are interested in IoTDB. However, the development threshold of IoTDB may be difficult for some newcomers who have no development experience.
    So we think if some community members are familiar with some aspects of IoTDB and interested in developing new people. They can be community mentors to help these newcomers by explaining some code and introducing some simple issues etc.
    We can start an enrollment program to recruit mentors, and after that start a vote about whether they can be the mentors.

  4. About IoTDB publicity
    For a long time, due to the lack of special attention to publicity, the effect of IoTDB publicity is not good. This also leads to the lack of contributors and the unknown situation of IoTDB.
    Therefore, next we can try to put IoTDB's promotional materials, documents and conference videos like the meetup video on more platforms, like IoTDB website, WeChat official account, Bilibili or even Tiktok.

...