Hi all, I would like to add IPv6 support as another candidate item for Apache IoTDB 2.0.12.
The implementation has been completed, and the corresponding PR has already been merged. It enables IoTDB to be deployed and used in IPv6 environments while maintaining compatibility with IPv4 deployments. Best regards, Haonan Hou On 2026/07/22 10:31:20 Yuan Tian wrote: > Hi all, > > Now that the rc/2.0.11 branch has been cut and the feature scope for > 2.0.11 is frozen, I would like to start an early discussion about > candidate work for Apache IoTDB 2.0.12. > > As a starting point, below is an initial list of candidates from the > query area and closely related schema work. > > This is an initial candidate list rather than a commitment or a release > decision. Inclusion in 2.0.12 will depend on community consensus and the > readiness of the design, implementation, review, documentation, > compatibility assessment, and testing. > > Query functions and analytics: > > - Add the pattern_match table-valued function for time-series trend > matching in the table model. > - Add more built-in statistical aggregate functions to the table model, > including the Pearson correlation coefficient. > - Add an optional SLIDE parameter to the CAPACITY table-valued function. > - Add the XCorr function for time-series cross-correlation analysis. > - Add the FFT function for frequency-domain analysis. > - Add built-in HighPass and LowPass filtering functions. > - Add a built-in M4 table-valued function. > - Add built-in rate, increase, irate, and delta aggregate functions. > > Query performance and resource efficiency: > > - Optimize full-table queries with ORDER BY time and LIMIT in the table > model. > - Reduce memory consumption for full-table queries in the table model. > > Operability and reliability: > > - Improve the availability of SHOW QUERIES under query-memory pressure. > The exact resource reservation or isolation mechanism still needs > further discussion. > > Metadata and schema: > > - Add high-availability support for template operations in the tree > model. > > Comments on the priorities, scope, designs, and any missing query-related > items are very welcome. > > I would also like to invite contributors and community members working > on the storage engine, AINode, Pipe and data synchronization, > metadata and schema, cluster management, and other areas to share the > features, improvements, performance work, or important fixes they would > like to propose for 2.0.12. > > Please also raise any concerns about whether a proposed item is > appropriate for the 2.0.12 release line. > > Once the initial input has been collected, I can summarize the candidate > items in this thread for another round of community discussion. > > Looking forward to your thoughts and proposals. > > Best regards, > Yuan Tian >
