Thank you very much for listening 😊 Chris
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> ________________________________ From: Yuan Tian <[email protected]> Sent: Thursday, 02 July 2026 10:52:43 To: [email protected] <[email protected]> Subject: Re: Planned Feature List for IoTDB 2.0.11 Hi Chris, Thanks for clarifying. The PLC4X example you mentioned is very helpful for me. That is less convenient, but I can see why it matters for building a truly open community. We still have a lot to improve here. Your point about trademark issues is also a good reminder. If contributors themselves do not clearly separate Apache IoTDB from company products in daily work, then it becomes even harder for marketing, sales, or other teams to understand that boundary. This is not something that can be solved just by saying “we did not mean it that way”. It needs clearer habits and processes. I think we can start with something practical: important features, release scope, and design tradeoffs should be brought to the dev list or GitHub issues earlier. If some discussion starts in company-internal tools, we should summarize the background and options in public before it becomes a decision, so the community has a real chance to join and challenge it. This will cost some convenience, but you are right: if we want the project to be healthy in the long run, that cost is worth paying. Thanks again for being direct about this. It is not always comfortable to hear, but I think it is important for us. Best regards, ---------------------- Yuan Tian On Thu, Jul 2, 2026 at 4:20 PM Christofer Dutz <[email protected]> wrote: > HI Yuan, > > I wasn’t suggesting to bridge Timecho’s internal Feishu instance with the > ASF. > That would be bad in many ways and I agree the challenge here is and > always has been: > Fighting the convenience of using one tool for corporate and open-source > stuff (and accepting some people are excluded) > > When I started PLC4X at codecentric the only others were codecentric > employees (most in the same office as me) > I insisted on only answering their questions if they ask them on the list. > That was odd and less convenient, but important for growing a truly > diverse community. > > I also think most of the recent trademark related issues coming up here > were directly related to this convenience. > If people don’t mentally know and understand where the line is between a > corporate product and an open-source project, how can you expect marketing > to know? > When marketing can’t draw the line, that’s where such problems arise. > > Yes: Ideally people would invest more time and sacrifice convenience for > the sake of community, but I know that many businesses don’t want to afford > that. > > My ideas regarding this universal exchange tool would possibly help the > good way to be less inconvenient. > > But I should mention that I’m observing how this project is operating with > two hats on right now: > > * > A PMC member who feels excluded from the party and > * > As a board member observing a company executing (from my perspective) > undue influence on an Apache project. > > > Chris > > > Von: Yuan Tian <[email protected]> > Datum: Donnerstag, 2. Juli 2026 um 03:20 > An: [email protected] <[email protected]> > Betreff: Re: Planned Feature List for IoTDB 2.0.11 > > Hi Chris, > > I think this direction is very interesting, especially the translation part > and the idea that people could participate using the client and language > they are most comfortable with, while the ASF still keeps a public and > auditable record. > > At the same time, I see one difficult boundary here. > > For many long-lived open source projects, there is often a company with a > large group of contributors behind the project. This has clear benefits: it > can provide sustained engineering effort, keep the project moving forward, > and maintain a high level of code activity over time. > > But there is also a downside. Day-to-day coordination can very easily > happen in the company’s internal tools, such as Feishu/Lark, because that > is where people already work. The hard part is that those spaces are > usually mixed: some discussions are about the open source project and > should be shared with the community, while others may involve company > operations, customers, internal planning, or other confidential > information. > > So even if the ASF pushes AI tooling at a higher level, I feel it would be > very risky for an ASF agent to directly access a company’s Feishu groups, > internal documents, or knowledge bases and decide what should be extracted > or shared. From a company perspective, the confidentiality and compliance > risks would be high, and I imagine it would be difficult for many > commercial companies to agree to or actively drive this. > > Slack may be a somewhat different case, and probably carries less risk. At > least for many Chinese companies, Slack is rarely the main internal > communication tool, so discussions happening there are more likely to > already be open-source or community-oriented. In the IoTDB case, the Slack > workspace itself does not really have a company-internal nature in the same > way that Feishu/Lark does. So bridging or improving > translation/searchability for public community channels such as Slack may > be much more feasible than trying to connect ASF tooling directly to > company-internal systems. > > For me, the safer and more practical direction may be to improve the > process at the boundary: make sure important project proposals, design > decisions, release planning, and conclusions are brought back to the dev > list or GitHub issues early enough, instead of trying to automatically > bridge everything from private company channels. > > So yes, I do think better multi-client and translation support could help a > lot for public ASF/community channels. I am just less sure that it can > fully solve the private-company-channel part, unless the boundary between > public project discussion and internal company discussion is handled very > carefully. > > Best regards, > ---------------------- > Yuan Tian > > On Wed, Jul 1, 2026 at 11:18 PM Christofer Dutz <[email protected] > > > wrote: > > > HI Yuan, > > > > Well this is a pattern I am observing with a lot of projects at Apache > > that have strong Chinese core communities. > > I know that Email is not the medium of choice for all. For me email is > one > > option that solves the problem of > > Allowing anyone, anywhere to participate fully with a wide variety of > > tools (Email Clients, Web-Email-Clients)… > > > > I would really love to see us possibly change away from Email as the only > > fully accepted option to something where Email, Slack, WeChat, Feishu is > > just one option. > > > > I’d envision a system where we as the ASF still have all the things on > > file, but allow anyone to participate with whatever client makes him/her > > happy. > > > > During my time at Timecho I was windblown by the ability to communicate > > with my Chinese colleagues in English while they wrote in Chinese and > > having the entire system take care of translations. This is something > where > > I also see potential of using some of our AI budget towards. > > > > Assuming we had such a system, which allows anyone to participate in any > > discussion using whatever tool he prefers in any language he prefers, > would > > this motivate people to come out of hiding behind these closed tools? > > > > If not … it’s not really worth the effort of me putting energy into > > something like this at board level. > > > > Chris > > > > > > Von: Yuan Tian <[email protected]> > > Datum: Mittwoch, 1. Juli 2026 um 14:30 > > An: [email protected] <[email protected]> > > Betreff: Re: Planned Feature List for IoTDB 2.0.11 > > > > Hi Chris, > > > > Thanks for saying this, and I don’t think you are causing waves. I > > understand the concern. > > > > We are also aware that this is something we need to improve. A lot of > > detailed communication still happens in WeChat and Feishu/Lark, and that > > can easily make people outside those channels feel disconnected. That is > > not the community experience we want. > > > > We have been trying to move more discussions back to the public Apache > > channels. Recently, some feature discussions have already happened on the > > dev list and GitHub issues, for example FFT, LCA, and alias support in > > GROUP BY / ORDER BY. It is still not enough, but we are trying to make > > important design, feature, and release-scope discussions visible and > > traceable there. > > > > Sending the planned items before each release is also intended as a small > > step in that direction. The hope is that the community can see the > proposed > > scope earlier, comment on it, adjust it, and, if anyone is interested in > > working on or helping with a certain release-note item, discuss it openly > > on the dev list as well. > > > > Suggestions from you or from the ASF side are very welcome. We would > really > > appreciate guidance on how to make this process easier for contributors > who > > are not in the China-side chat channels, and we will keep working on > > improving this. > > > > Best regards, > > --------------------- > > Yuan Tian > > > > On Wed, Jul 1, 2026 at 8:23 PM Christofer Dutz < > [email protected]> > > wrote: > > > > > Hi Yuan, > > > > > > Thanks for that explanation … I also don’t want to appear intentionally > > > causing waves, it’s just that it’s really challenging to stay connected > > > with the project with all the discussions and things happening on > WeChat > > > and Feishu/Lark. For people from outside of China it’s almost > impossible > > to > > > feel fully integrated. > > > > > > I’d love to change this, if there’s anything I/we can do from the side > of > > > the ASF. > > > > > > Chris > > > > > > > > > Von: Yuan Tian <[email protected]> > > > Datum: Mittwoch, 1. Juli 2026 um 14:00 > > > An: [email protected] <[email protected]> > > > Betreff: Re: Planned Feature List for IoTDB 2.0.11 > > > > > > Hi Chris, > > > > > > I’m sorry it came across that way, and thank you for calling this out. > > > > > > The intention here was not to bypass the PMC or present a final project > > > plan. This list was meant as an initial draft collected from the > current > > > development work, so that we can discuss it openly on the dev list and > > make > > > sure the release notes and scope are visible to everyone. > > > > > > You are right that project planning should happen with the community > and > > > the PMC, not be dropped in as a finished decision. We should have > worded > > > this more clearly as a proposal / starting point for discussion. > > > > > > Your input is very important to the project, and I’m sorry this made > you > > > feel excluded. Let’s treat this thread as the beginning of the planning > > > discussion for 2.0.11. We welcome you and other PMC/community members > to > > > adjust the list, add missing items, or challenge anything that should > not > > > be part of this release. > > > > > > I really appreciate the work you have put into IoTDB and I do not want > > our > > > process to make you feel sidelined. > > > > > > Best regards, > > > ---------------------- > > > Yuan Tian > > > > > > On Wed, Jul 1, 2026 at 4:07 PM Christofer Dutz < > > [email protected]> > > > wrote: > > > > > > > Where has it's list been planed? > > > > > > > > Really odd how excluded you folks make me feel on this project 😔 > > > > > > > > Plans about the project should be created by the PMC and not be > dropped > > > on > > > > the project from the side lines. > > > > > > > > Chris > > > > > > > > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> > > > > ________________________________ > > > > From: Yuan Tian <[email protected]> > > > > Sent: Wednesday, 01 July 2026 08:12:35 > > > > To: [email protected] <[email protected]> > > > > Subject: Re: Planned Feature List for IoTDB 2.0.11 > > > > > > > > Hi yiru, > > > > > > > > Thanks for the update, we'll keep working on it. > > > > > > > > > > > > Best regards, > > > > -------------------- > > > > Yuan Tian > > > > > > > > On Wed, Jul 1, 2026 at 12:32 PM 王艺儒 <[email protected]> wrote: > > > > > > > > > Hi all, > > > > > Below is the planned feature list for the IoTDB 2.0.11 release. The > > > > > scheduled code freeze date for this version is July 15th. After > code > > > > > freeze, we will conduct comprehensive testing and validation for > all > > > > newly > > > > > added and optimized features, followed by the official release > > > afterward. > > > > > > > > > > Planned features are listed as follows: > > > > > 1. Upgrade the project JDK version to 17 and update relevant > > > third-party > > > > > dependencies > > > > > 2. Add official Node.js client, which will be maintained in the > > > > > iotdb-client-nodejs repository > > > > > 3. Introduce automatic repair capability for partition tables > > > > > 4. Add backward filling function for the table model > > > > > 5. Add logical view capability for the table model > > > > > 6. Add mTLS support for Thrift clients > > > > > 7. Add count database syntax in the table model to count the total > > > number > > > > > of databases > > > > > 8. Introduce built-in table-valued function read_tsfile for the > table > > > > > model, enabling direct reading and querying of specified TsFile > > content > > > > via > > > > > SQL statements > > > > > 9. Restrict SQL queries of the table model to only allow SELECT > > > > statements > > > > > 10. Optimize the show timeseries command in the tree model to > support > > > > > sorting by measurement name > > > > > 11. Enable high availability for five management modules: database > > > > > management, table management, device management, writable view > > > management > > > > > and TTL management > > > > > 12. Support hot reloading of partial cluster runtime > configurations; > > > > > configuration changes can take effect without restarting the > cluster > > > > > > > > > > Everyone is welcome to propose additional release-note items to be > > > > > included in this release iteration. > > > > > As the PM in charge of IoTDB community version iteration > management, > > I > > > > > welcome you to contact me anytime with any questions or comments. > > > > > > > > > > Best regards, > > > > > Yiru Wang > > > > > > > > > > -------------------------------------- > > > > > 各位社区成员： > > > > > 以下为 IoTDB 2.0.11 版本规划迭代的功能清单，本次版本预计于 7 月 15 > > > > > 日完成代码冻结。代码冻结后，我们将对所有版本新增及优化功能开展全面测试与验证，测试完成后正式对外发布。 > > > > > > > > > > 具体规划功能如下： > > > > > 1. 将项目 JDK 版本升级至 17，并更新相关第三方依赖包 > > > > > 2. 新增 Node.js 官方客户端，存放在 iotdb-client-nodejs 仓库中 > > > > > 3. 新增分区表自动修复功能 > > > > > 4. 表模型新增后值填充功能 > > > > > 5. 表模型新增逻辑视图功能 > > > > > 6. 新增支持 Thrift 客户端 mTLS > > > > > 7. 表模型中新增统计库数量的 count database 语法支持 > > > > > 8. 表模型新增内置表值函数 read_tsfile，支持通过 SQL 语句直接读取并查询指定 TsFile 文件内容 > > > > > 9. 表模型支持查询 SQL 仅允许使用 SELECT 查询语句 > > > > > 10. 树模型优化 show timeseries 命令支持按测点名称排序的能力 > > > > > 11. 优化数据库管理、表管理、设备管理、可写视图管理、TTL管理 五大模块支持高可用 > > > > > 12. 支持集群运行态部分配置项热加载，配置变更无需重启集群即可生效 > > > > > > > > > > 欢迎大家提出建议，增补需要纳入本次版本迭代的更新条目。 > > > > > 我是负责 IoTDB 社区版本迭代管理的 PM，大家如有疑问或意见，欢迎随时与我沟通。 > > > > > > > > > > 此致 > > > > > 王艺儒 > > > > > > > > > > > > > > > > > > > >
