产品迭代进展(Product Iteration Progress) [2024-05-13]
hnwyllmm opened this issue · comments
This issue will be updated weekly.
[中文版] | [English]
| 更新内容 | 更新日期 |
|---|---|
| OceanBase 4.3.0 已发布 | 2024-04-07 |
| ODC 4.2.4 已发布 obdiag 2.0.0 已发布 obdiag 2.1.0 进行中 ob-operator 2.2.0 已发布 ob-operator 2.2.1 进行中 oceanbase-dashboard 0.2.0 已发布 oceanbase-dashboard 0.3.0 进行中 |
2024-04-16 |
| obdeploy 2.8.0 已发布 OCP-CE 预计发布时间从5月7号调整为5月20号 OMS 4.2.3 已发布 OMS 4.2.4 需求收集中 logproxy V2.0.1_BP2 已发布 |
2024-04-22 |
| obdeploy 2.9.0 开发中 ob-operator dashboard 0.2.1 已发版 obdiag 2.1.0 已发布 2.2.0 迭代中 OMS 4.2.4 开发中 oblogproxy 2.0.2 开发中 |
2024-05-13 |
OceanBase
- 4.2.3 已发布：支持CPU全局的前后台任务的资源隔离机制，新增支持ipv6，支持将备份数据存储在s3上等，同时也提供系统日志压缩、logminer等功能提升产品的易用性。
- 4.3 4.3版本推出列存引擎，实现行存、列存数据存储一体化。新增物化视图功能，通过预计算存储视图的查询结果提升实时查询性能。同时新版本内核也扩展了Online DDL、新增支持了租户克隆、索引使用监控等功能。
obdeploy
- V2.6.1 已发布;
- V2.6.2 已发布：该版本为 BUGFIX 版本，主要修复本月收到的部分问题反馈。
- V2.7.0 已发布：该版本主要是支持非部署组件(obclient/jre)安装，进一步提供JAVA产品(OCP、OCP-Express）的易用性。
- V2.8.0 已发布：该版本主要是支持接管含有OBShell的Oceanbase集群。
- V2.9.0 预计6月初发版
ob-operator
- V2.1.2 已发布：该版本主要Standalone模式。目前大部分ob-operator用户是希望替换正在使用的mysql。该模式可以在不支持固定IP的情况下实现POD重建不丢失，进一步降低用户使用门槛。
- V2.2.0 已发布：该版本主要适配4.3.0新特性，不再依赖网络组件实现自动容灾。
- V2.2.1 开发中: 该版本主要实现集群可迁移至 ob-operator 管理，增加操作类资源，同时进行实用的功能增强，在集群部署完成之后可修改资源和存储挂载。
- Dashboard V0.2.0 已发版：该版本将补齐租户管理相关功能，包括租户创建、备份、恢复等。
- Dashboard V0.2.1 已发版：在“连接”选项卡中添加了对连接集群系统和租户的支持。
- Dashboard V0.3.0 开发中：该版本将增加 obproxy 管理和告警功能。
OBShell
- V4.2.3 已发布,主要优化客户端交互体验。
- V4.2.3 BP1 迭代中,主要优化客户端动画展示等。推出 OBShell-SDK-GO 方便 go语言开发者接入；OBShell-SDK-Python 开发中。
ODC
- V4.2.3 已发布，引入数据归档改进、任务日志查看与编辑、无锁结构变更以及账号锁定和表重命名功能。增强项目协同，用户可申请权限，绑定数据源，新增安全管理员和参与者角色，工单可共享URL。SQL Check和全链路TRACE得到优化，前者可定位问题SQL，后者可深入分析慢查询。MySQL数据源新增导入导出，模拟数据支持扩增至1亿行。
- V4.2.4 2024/4/3 发布，带来OceanBase 4.2.2、Oracle和Doris支持，71个新的代码片段和字典视图的自动补全。同构数据库结构比对、OBOracle分区计划配置、提升数据归档和清理效率。安全增强涵盖更多SQL规则、库访问权限、通知功能。SSO现支持LDAP，易用性提升体现在优化的数据库选择和个人配置，桌面版允许大容量数据导出。详见 ODC CHANGELOG 。
OceanBase 敏捷诊断工具(obdiag)
- V1.6.1 已发布：主要支持巡检、场景采集套餐的热更新和场景化信息采集优化。
- V1.6.2 已发布：主要移除了perf信息采集功能中的pstack收集，增加了CPU高场景采集日志。
- V2.0.0已发布：主要支持内核PX诊断增强，同时完成根因分析技术改进，降低共建开发者的学习成本, 预计4月初发布。
- V2.1.0 已发布：新增1个基础采集tabledump功能，新增3个根因分析场景（集群无主问题根因分析、通用事务问题根因分析、建索引报错问题根因分析），4个优化项(sql/ssh执行器优化、日志分析对文件压缩传输、cpu高场景信息采集优化、集群故障时不阻塞采集)
- V2.2.0 迭代中：主要是扩充根因分析场景以及新增tabledump采集功能
OMS
- V4.2.3 已发布：4.1.0 CE版本链路迁移、HBase-> OceanBase 旁路写入、HBase 2.4.13、TiDB 2.x 3.x支持、更换数据源，于4月18日发布
- V4.2.4 迭代：新增支持 HBase->OBKV 旁路导入，支持社区版 HBase V2.x、TiDB V2.x 和 V3.x、GreenPlum V5.1、PostgreSQL V11.x、V13.x、V14.x、V15.x 和 V16.x 等版本，支持单点登录、更换数据源、统一日志保留时间、数据库通配，以及 OMS V4.1.0-CE 通过特殊升级步骤直接升级至 V4.2.3-CE。预计6月27日发版
logproxy
- V2.0.1_BP1 已发布：新增支持源端 observer v4.2.2、v4.2.1.3及以上版本，于3月27日发布
- V2.0.1_BP2 已发布：新增支持 OceanBase 数据库 v4.3.0 版本，于4月16日发布
- V2.0.2 开发中：binlog 模式新增运维功能
OCP-CE
- V4.2.2 已发布：主要支持ObServer 4.2.2 CE，并且支持监控大盘等新增功能；
- V4.3.0 迭代中：主要功能主备库切换、OBS/S3 适配、活跃告警处理 & 优化告警消除逻辑、 CPU 超卖等预计 5月20号发布。
[English] | [中文版]
| Updated Content | Date |
|---|---|
| OceanBase 4.3.0 published | 7/4/2024 |
| ODC 4.2.4 published ob-operator 2.2.0 published ob-operator 2.2.1 in progress obdiag 2.0.0 published obdiag 2.1.0 in grogress oceanbase-dashboard 0.2.0 published oceanbase-dashboard 0.3.0 in grogress |
16/4/2024 |
| obdeploy 2.8.0 published The expected release time of OCP-CE is adjusted from May 7 to May 20 OMS 4.2.3 has been released OMS 4.2.4 requirements are being collected logproxy V2.0.1_BP2 has been released |
22/4/2024 |
| obdeploy 2.9.0 in progress ob-operator dashboard 0.2.1 released obdiag 2.1.0 released, 2.2.0 in progress OMS 4.2.4 in progress oblogproxy 2.0.2 in progress |
13/5/2024 |
OceanBase
- 4.2.3 released: V4.2.3 supports global CPU resource isolation for background and foreground tasks, adds support for IPv6, and allows you to back up data to S3. It also enhances usability with features like system log compression and LogMiner.
- 4.3 V4.3 introduces a columnar storage engine, which allows the database to simultaneously support both row-based (row store) and columnar (column store) data storage methods. It adds support for materialized views to enhance real-time query performance by precomputing and storing query results. V4.3 also enhances the kernel features such as online DDL, tenant cloning, and index usage monitoring.
obdeploy
- V2.6.1 has been released;
- V2.6.2 has been released: This is the BUGFIX version, which mainly fixes some problem feedback received this month. It is expected to be released on March 7th.
- V2.7.0 has been released: This version mainly supports the installation of non-deployment components (obclient/jre) and further provides JAVA products (OCP , OCP-Express) ease of use.
- V2.8.0 has been released: It mainly supports taking over Oceanbase clusters containing OBShell.
- V2.9.0 Expected to be released in early June.
ob-operator
- V2.1.2 released: This version is mainly in Standalone mode. Currently, most ob-operator users want to replace the MySQL they are using. This mode can achieve POD reconstruction without loss when fixed IP is not supported, further reducing the user threshold.
- V2.2.0 released: This version mainly adapts to the new features of 4.3.0 and no longer relies on network components to achieve automatic disaster recovery.
- V2.2.1 is under developing: This release will provide the ability to migrate OceanBase Cluster to cloud environment and managed by ob-operator, provide operation resources, and enhance the ability to modify resource and storage mounts after cluster deployed.
- Dashboard V0.2 released: This version will complete tenant management-related functions, including tenant creation, backup, recovery, etc.
- Dashboard V0.2.1 released: Added support for connecting cluster sys and tenant in Connection tab.
- Dashboard V0.3.0 is under developing：This release will integrate alertmanager to provide the ability to handle alarms and operations of obproxy.
OBShell
- V4.2.3 has been released, focusing on enhancing the user interaction experience.
- V4.2.3 is under iteration, mainly improving client animation display and more. Launched OBShell-SDK-GO to facilitate access for go language developers; OBShell-SDK-Python is under development.
ODC
- V4.2.3 released with improved data archiving, editable task settings, lock-free structural modifications including account locks and table renames. Enhanced project collaboration introduces permission requests, data source-project binding, new roles for security and participation, and ticket sharing via URLs. SQL Check can now pinpoint risk issues. MySQL data source gains import/export capabilities. Full-link TRACE now analyzes slow SQL, and data mocking scales to 100 million rows.
- V4.2.4 released on 2024/4/3, supporting OceanBase 4.2.2, Oracle, Doris, and offering 71 new code snippets. Homogeneous database structure comparison with DIFF previews and script downloads, OBOracle's configurable partitioning, improved data archiving/cleansing, and more SQL checks optimize security. SSO includes LDAP integration. Enhancements in usability with refined database selectors and personal settings boost the desktop version's large data export capabilities. See ODC CHANGELOG for details.
OceanBase Diagnostic Tool (obdiag)
- V1.6.1 released : It mainly supports inspections, hot updates of scene collection packages and scene-based information collection optimization.
- V1.6.2 released: it mainly removed the pstack collection in the perf information collection function and added the cup high scene collection log.
- V2.0.0released: It mainly supports kernel PX diagnostic enhancement, and also completes root cause analysis technology improvements to reduce the learning cost of co-build developers. Expected to be released in early April.
- V2.1.0 released:Add 1 basic collection tabledump function, add 3 root cause analysis scenarios (root cause analysis for cluster no rootservice problems, root cause analysis for general transaction problems, and root cause analysis for index error problems), and 4 optimization items (SQL/ssh executor optimization, log analysis for file compression transmission, CPU high scenario information collection optimization, and non blocking collection during cluster failures)
- V2.2.0 iteration in progress: Mainly to expand root cause analysis scenarios and add tabledump collection function.
OMS
- V4.2.3 published: Mainly supports access telemetry, 4.1.0 CE version link migration, hbase to oceanbase bypass writing, hbase 2.4.13, tidb 2.x 3.x support, data source replacement, published on April 18
- V4.2.4 iteration: Added support for HBase->OBKV bypass import, supporting community version HBase V2.x, TiDB V2.x and V3.x, GreenPlum V5.1, PostgreSQL V11.x, V13.x, V14.x, V15.x and V16.x and other versions support single sign-on, data source replacement, unified log retention time, database wildcarding, and OMS V4.1.0-CE can be directly upgraded to V4.2.3-CE through special upgrade steps. Expected to be released on June 27
logproxy
- V2.0.1_BP1 published: Added support for source observer v4.2.2, v4.2.1.3 and above
- V2.0.1_BP2 published: Added support for OceanBase database v4.3.0, released on April 22
- V2.0.2 in progress: new operation and maintenance functions in binlog mode
OCP-CE
- V4.2.2 Primarily supports ObServer 4.2.2 CE, and includes support for new features such as monitoring dashboards.
- V4.3.0 is being iterated: main functions such as active and standby database switching, OBS/S3 adaptation, active alarm processing & optimized alarm elimination logic, CPU oversold, etc. are expected to be released on May 20.
为啥4.3比4.2.3更早发布
现在是双主线研发4.3.x和4.2.x。
no progress last week.
You can update the latest progress to the last comment every week, at the same time update the first one to the latest.
So we can view all status.
You can update the latest progress to the last comment every week, at the same time update the first one to the latest.
So we can view all status.
I'll update the change note here:
Will the release time of the new OCP version change ? I can use it on May 20?
Will the release time of the new OCP version change ? I can use it on May 20?
The release date isn't changed.