This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new b7294b23bc3 Refactor module naming consistency for infra-url
components (#37060)
b7294b23bc3 is described below
commit b7294b23bc31eebcda69d1c32af2772938e7ccaf
Author: Liang Zhang <[email protected]>
AuthorDate: Mon Nov 10 00:58:54 2025 +0800
Refactor module naming consistency for infra-url components (#37060)
* Refactor module naming consistency for infra-url components
- Rename shardingsphere-infra-url-type-zookeeper to
shardingsphere-infra-url-zookeeper
- Rename shardingsphere-infra-url-type-etcd to
shardingsphere-infra-url-etcd
- Update dependency references in distribution/jdbc/pom.xml
This change aligns the naming convention with other infra-url modules
such as shardingsphere-infra-url-classpath, improving module
naming consistency across the project.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
* Update README.md
---
README.md | 138 ++++++++++++++++++++++++++++++--------
README_ZH.md | 140 +++++++++++++++++++++++++++++++--------
distribution/jdbc/pom.xml | 12 ++--
infra/url/type/etcd/pom.xml | 2 +-
infra/url/type/zookeeper/pom.xml | 2 +-
5 files changed, 233 insertions(+), 61 deletions(-)
diff --git a/README.md b/README.md
index 4634f49d18c..0247bd992a7 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,6 @@
-## [Distributed SQL transaction & query engine for data sharding, scaling,
encryption, and more - on any database.](https://shardingsphere.apache.org/)
+## [Apache ShardingSphere - Enterprise Distributed Database
Ecosystem](https://shardingsphere.apache.org/)
+
+Building the standards and ecosystem on top of heterogeneous databases,
empowering enterprise data architecture transformation
**Official Website:**
[https://shardingsphere.apache.org/](https://shardingsphere.apache.org/)
@@ -52,22 +54,63 @@
<hr>
-Apache ShardingSphere is a distributed SQL transaction & query engine that
allows for data sharding, scaling, encryption, and more - on any database. Our
community's guiding development concept is Database Plus for creating a
complete ecosystem that allows you to transform any database into a distributed
database system.
+Apache ShardingSphere is positioned as **Database Plus**, a standard and
ecosystem built on top of heterogeneous databases. As an operating system layer
above databases, ShardingSphere does not create new databases but focuses on
maximizing the computing capabilities of existing databases, providing unified
data access and enhanced computing capabilities.
+
+**Database Plus Core Concept**: By building a standardized and scalable
enhancement layer above databases, it makes heterogeneous databases as simple
to use as a single database, providing unified governance capabilities and
distributed computing capabilities for enterprise data architectures.
+
+**Connect, Enhance, and Pluggable** are the three core pillars of Apache
ShardingSphere:
+
+- **Connect:** Building database upper-layer standards, quickly connecting
applications with multi-modal heterogeneous databases through flexible
adaptation of database protocols, SQL dialects, and storage formats, providing
unified data access experience;
+
+- **Enhance:** As a database computing enhancement engine, transparently
providing enterprise-grade capabilities including distributed computing (data
sharding, readwrite-splitting, SQL federation), data security (encryption,
masking, audit), traffic control (circuit breaker, rate limiting), and
observability (monitoring, tracing, analysis);
+
+- **Pluggable:** Adopting a micro-kernel + 3-layer pluggable architecture to
achieve complete decoupling of kernel, functional components, and ecosystem
integration. Developers can flexibly customize unique data architecture
solutions that meet enterprise needs, just like building with LEGO blocks.
+
+**Differentiation Advantages**:
+- **vs Distributed Databases**: More lightweight, protecting existing
investments, avoiding vendor lock-in
+- **vs Traditional Middleware**: Richer features, more complete ecosystem,
more flexible architecture
+- **vs Cloud Vendor Solutions**: Support multi-cloud deployment, avoid
technology binding, autonomous and controllable
+
+ShardingSphere became an [Apache](https://apache.org/index.html#projects-list)
Top-Level Project on April 16, 2020, and has been adopted by [19,000+
projects](https://github.com/search?l=Maven+POM&q=shardingsphere+language%3A%22Maven+POM%22&type=Code)
worldwide.
+
+### DUAL-ACCESS ARCHITECTURE DESIGN
+
+<hr>
+
+ShardingSphere adopts a unique dual-access architecture design, providing two
access ends - JDBC and Proxy - that can be deployed independently or in hybrid
deployment, meeting diverse requirements for different scenarios.
-It focuses on repurposing existing databases, by placing a standardized upper
layer above existing and fragmented databases, rather than creating a new
database.
+#### ShardingSphere-JDBC: Lightweight Access End
-The goal is to provide unified database services and minimize or eliminate the
challenges caused by underlying databases' fragmentation.
-This results in applications only needing to communicate with a single
standardized service.
+**Positioning**: Lightweight Java framework, enhanced JDBC driver
-The concepts at the core of the project are `Connect`, `Enhance` and
`Pluggable`.
+**Core Features**:
+- **Client-side direct connection**: Shares resources with applications,
decentralized architecture
+- **High performance, low overhead**: Direct database connection with minimal
performance loss
+- **Complete compatibility**: Compatible with all ORM frameworks (MyBatis,
JPA, Hibernate, etc.)
+- **Zero additional deployment**: Provided as JAR package, no independent
deployment and dependencies required
-- `Connect:` Flexible adaptation of database protocol, SQL dialect and
database storage. It can quickly connect applications and heterogeneous
databases.
-- `Enhance:` Capture database access entry to provide additional features
transparently, such as: redirect (sharding, readwrite-splitting and shadow),
transform (data encrypt and mask), authentication (security, audit and
authority), governance (circuit breaker and access limitation and analyze, QoS
and observability).
-- `Pluggable:` Leveraging the micro kernel and 3 layers pluggable mode,
features and database ecosystem can be embedded flexibly. Developers can
customize their ShardingSphere just like building with LEGO blocks.
+**Use Cases**: High-performance Java applications, integrated deployment with
business applications, pursuing ultimate performance
-ShardingSphere became an [Apache](https://apache.org/index.html#projects-list)
Top-Level Project on April 16, 2020.
+#### ShardingSphere-Proxy: Enterprise Access End
-So far, ShardingSphere has been used by over [15,000 projects on
GitHub](https://github.com/search?l=Maven+POM&q=shardingsphere+language%3A%22Maven+POM%22&type=Code).
+**Positioning**: Transparent database proxy, independently deployed server-side
+
+**Core Features**:
+- **Static entry point**: Independent deployment from applications, providing
stable database access entry
+- **Heterogeneous language support**: Supports any MySQL/PostgreSQL protocol
compatible client
+- **DBA friendly**: Database operation and maintenance management interface,
convenient for O&M personnel
+- **Enterprise-grade features**: Supports cluster deployment, load balancing,
failover
+
+**Use Cases**: Heterogeneous language environments, database operation and
maintenance management, enterprise applications requiring unified access entry
+
+#### Hybrid Architecture Advantages
+
+By hybridizing ShardingSphere-JDBC and ShardingSphere-Proxy with unified
configuration through the same registry center, you can flexibly build
application systems suitable for various scenarios:
+
+- **Architectural flexibility**: Architects can freely adjust the optimal
system architecture
+- **Scenario adaptability**: Select the most suitable access method according
to different business scenarios
+- **Unified management**: Single configuration, multi-end collaboration,
simplifying O&M complexity
+- **Progressive evolution**: Support smooth evolution path from JDBC to Proxy
### AI ABSTRACTION
@@ -114,18 +157,18 @@ We deeply appreciate [community
contributors](https://shardingsphere.apache.org/
##
-### STATUS👀
+### PROJECT STATUS
<hr>
-:white_check_mark: Version 5.5.2: released :tada:
+:white_check_mark: **Version 5.5.3-SNAPSHOT**: Actively under development
:tada:
🔗 For the release notes, follow this link to the relevant [GitHub
page](https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md).
-:soon: Version 5.5.3
+:soon: **Version 5.5.3**
-We are currently working towards our 5.5.3 milestone.
-Keep an eye on the [milestones
page](https://github.com/apache/shardingsphere/milestones) of this repo to stay
up to date.
+We are currently developing version 5.5.3, which includes multiple security
enhancements and performance optimizations.
+Keep an eye on the [milestones
page](https://github.com/apache/shardingsphere/milestones) of this repo for the
latest development progress.
[comment]: <> (##)
@@ -151,12 +194,36 @@ Keep an eye on the [milestones
page](https://github.com/apache/shardingsphere/mi
##
-### How it Works
+### TECHNICAL ARCHITECTURE EVOLUTION
<hr>
-Apache ShardingSphere includes 2 independent products: JDBC & Proxy.
-They all provide functions of data scale-out, distributed transaction and
distributed governance, applicable in a variety of situations such as
Java-based isomorphism, heterogeneous language and Cloud-Native.
+Apache ShardingSphere adopts a micro-kernel + 3-layer pluggable architecture,
achieving complete decoupling of the kernel, functional components, and
ecosystem integration, providing developers with ultimate flexibility and
extensibility.
+
+#### Micro-Kernel + 3-Layer Pluggable Model
+
+**Core Layer**:
+- Query optimizer: Intelligent SQL routing and execution plan optimization
+- Distributed transaction: ACID transaction guarantees and consistency
coordination
+- Execution engine: Efficient distributed execution and result aggregation
+
+**Feature Layer**:
+- Data sharding, readwrite-splitting, federation query
+- Data encryption, data masking, SQL audit
+- Shadow database, observability, traffic control
+
+**Ecosystem Layer**:
+- Database protocol adaptation (MySQL, PostgreSQL, Oracle, etc.)
+- Registry center integration (ZooKeeper, ETCD, etc.)
+- Configuration management, service discovery, monitoring integration
+
+#### Technical Innovation Highlights
+
+**Complete Decoupling Architecture**:
+- Database types completely decoupled, supporting rapid integration of new
databases
+- Functional modules completely decoupled, supporting on-demand feature
combination
+
+Apache ShardingSphere consists of two access ends - JDBC and Proxy - that can
be deployed independently or in hybrid deployment, providing unified
distributed database solutions for diverse application scenarios including Java
isomorphism, heterogeneous languages, and cloud-native environments.
### ShardingSphere-JDBC
@@ -198,17 +265,34 @@ Through the combination of ShardingSphere-JDBC &
ShardingSphere-Proxy together w
##
-### Solution
+### CORE FEATURE MATRIX
<hr>
-| *Solutions/Features* | *Distributed Database* | *Data Security* |
*Database Gateway* | *Stress Testing* |
-|----------------------|-------------------------|----------------------|-----------------------------------|------------------|
-| | Data Sharding | Data Encryption |
Heterogeneous Databases Supported | Shadow Database |
-| | Read/write Splitting | Row Authority (TODO) | SQL
Dialect Translate (TODO) | Observability |
-| | Distributed Transaction | SQL Audit (TODO) |
| |
-| | Elastic Scale-out | SQL Firewall (TODO) |
| |
-| | High Availability | |
| |
+#### Distributed Database Core Capabilities
+- **Data Sharding**: Horizontal sharding, vertical sharding, custom sharding
strategies, automatic sharding routing
+- **Read/Write Splitting**: Master-slave replication, load balancing,
failover, read weight configuration
+- **Distributed Transaction**: XA transactions, flexible transactions, Seata
AT integration, transaction propagation
+
+#### Data Security & Governance
+- **Data Encryption**: Field-level encryption, transparent encryption, key
management, encryption algorithm support
+- **Data Masking**: Sensitive data protection, masking strategy customization,
dynamic masking rules
+- **Access Control**: Fine-grained permissions, access control, SQL firewall,
security policies
+
+#### Database Gateway Capabilities
+- **Heterogeneous Databases**: MySQL, PostgreSQL, Oracle, SQL Server,
Firebird, etc.
+- **SQL Dialect Translation**: Cross-database SQL compatibility, dialect
adaptation, syntax conversion
+- **Protocol Adaptation**: Database protocol conversion, multi-protocol
support, communication optimization
+
+#### Full-link Stress Testing & Observability
+- **Shadow Database**: Stress testing data isolation, environment separation,
real data simulation
+- **Observability**: Performance monitoring, distributed tracing, QoS
analysis, metrics collection
+- **Traffic Analysis**: SQL performance analysis, traffic statistics,
bottleneck identification
+
+#### Enterprise-grade Features
+- **High Availability**: Cluster deployment, fault recovery, service
discovery, health checks
+- **Cloud Native**: Containerized deployment, Kubernetes integration, native
image support
+- **Monitoring & Alerting**: Real-time monitoring, alert notifications,
performance metrics, O&M dashboard
##
diff --git a/README_ZH.md b/README_ZH.md
index 3e259e9019a..e9089e98584 100644
--- a/README_ZH.md
+++ b/README_ZH.md
@@ -1,4 +1,6 @@
-## [ShardingSphere -
构建异构数据库上层的标准和生态](https://shardingsphere.apache.org/index_zh.html)
+## [Apache ShardingSphere -
企业级分布式数据库生态系统](https://shardingsphere.apache.org/index_zh.html)
+
+构建异构数据库上层的标准与生态，赋能企业数据架构数字化转型
**官方网站: https://shardingsphere.apache.org/**
@@ -52,18 +54,63 @@
<hr>
-Apache ShardingSphere 产品定位为 `Database Plus`，旨在构建异构数据库上层的标准和生态。
-它关注如何充分合理地利用数据库的计算和存储能力，而并非实现一个全新的数据库。ShardingSphere
站在数据库的上层视角，关注他们之间的协作多于数据库自身。
+Apache ShardingSphere 定位为 **Database
Plus**，是构建在异构数据库上层的标准与生态系统。作为数据库上层的操作系统，ShardingSphere
并非创造全新的数据库，而是专注于最大化现有数据库的计算能力，提供统一的数据访问入口和增强计算能力。
+
+**Database Plus
核心理念**：通过在数据库上层构建标准化、可扩展的增强层，让异构数据库像单一数据库一样简单使用，为企业数据架构提供统一的治理能力和分布式计算能力。
+
+**连接、增强、可插拔** 是 Apache ShardingSphere 的三大核心支柱：
+
+- **连接：** 构建数据库上层标准，通过灵活适配数据库协议、SQL 方言和存储格式，快速连接应用与多模式异构数据库，提供统一的数据访问体验；
+
+- **增强：**
作为数据库计算增强引擎，透明化提供分布式计算（数据分片、读写分离、联邦查询）、数据安全（加密、脱敏、审计）、流量控制（熔断、限流）以及可观测性（监控、追踪、分析）等企业级能力；
+
+- **可插拔：** 采用微内核 +
三层可插拔架构，实现内核、功能组件与生态对接的完全解耦，开发者可以像搭建积木一样，灵活定制符合企业需求的独特数据架构解决方案。
+
+**差异化优势**：
+- **vs 分布式数据库**：更轻量级、保护现有投资、避免厂商锁定
+- **vs 传统中间件**：功能更丰富、生态更完善、架构更灵活
+- **vs 云厂商方案**：支持多云部署、避免技术绑定、自主可控
+
+ShardingSphere 于 2020 年 4 月 16 日成为 [Apache
软件基金会](https://apache.org/index.html#projects-list) 顶级项目，已在全球范围内被 [19,000+
项目](https://github.com/search?l=Maven+POM&q=shardingsphere+language%3A%22Maven+POM%22&type=Code)采用。
+
+### 双接入端架构设计
+
+<hr>
+
+ShardingSphere 采用独特的双接入端架构设计，提供 JDBC 和 Proxy 两种既可独立部署又可混合部署的接入端，满足不同场景下的多样化需求。
+
+#### ShardingSphere-JDBC：轻量级接入端
-`连接`、`增强` 和 `可插拔` 是 Apache ShardingSphere 的核心概念。
+**定位**：轻量级 Java 框架，增强版 JDBC 驱动
-- `连接：`通过对数据库协议、SQL 方言以及数据库存储的灵活适配，快速的连接应用与多模式的异构数据库；
--
`增强：`获取数据库的访问流量，并提供流量重定向（数据分片、读写分离、影子库）、流量变形（数据加密、数据脱敏）、流量鉴权（安全、审计、权限）、流量治理（熔断、限流）以及流量分析（服务质量分析、可观察性）等透明化增强功能；
-- `可插拔：`项目采用微内核 +
三层可插拔模型，使内核、功能组件以及生态对接完全能够灵活的方式进行插拔式扩展，开发者能够像使用积木一样定制属于自己的独特系统。
+**核心特性**：
+- **客户端直连**：与应用程序共享资源，无中心化架构
+- **高性能低损耗**：直接数据库连接，性能损耗最小
+- **完全兼容**：兼容所有 ORM 框架（MyBatis、JPA、Hibernate 等）
+- **零额外部署**：以 JAR 包形式提供，无需独立部署和依赖
-ShardingSphere 已于 2020 年 4 月 16 日成为 [Apache
软件基金会](https://apache.org/index.html#projects-list)的顶级项目。
+**适用场景**：Java 高性能应用，与业务应用集成部署，追求极致性能
-迄今为止，已有超过 [15,000 个 GitHub
项目](https://github.com/search?l=Maven+POM&q=shardingsphere+language%3A%22Maven+POM%22&type=Code)采用了
ShardingSphere。
+#### ShardingSphere-Proxy：企业级接入端
+
+**定位**：透明化数据库代理，独立部署的服务端
+
+**核心特性**：
+- **静态入口**：独立于应用程序部署，提供稳定的数据库访问入口
+- **异构语言支持**：支持任意兼容 MySQL/PostgreSQL 协议的客户端
+- **DBA 友好**：数据库运维管理界面，便于运维人员操作
+- **企业级特性**：支持集群部署、负载均衡、故障转移
+
+**适用场景**：异构语言环境、数据库运维管理、需要统一访问入口的企业级应用
+
+#### 混合架构优势
+
+通过混合使用 ShardingSphere-JDBC 和
ShardingSphere-Proxy，并采用同一注册中心统一配置分片策略，能够灵活搭建适用于各种场景的应用系统：
+
+- **架构灵活性**：架构师可自由调整最佳系统架构
+- **场景适配性**：根据不同业务场景选择最适合的接入方式
+- **统一管理**：单一配置，多端协同，简化运维复杂度
+- **渐进式演进**：支持从 JDBC 到 Proxy 的平滑演进路径
### AI 总结
@@ -108,27 +155,51 @@ ShardingSphere 已于 2020 年 4 月 16 日成为 [Apache 软件基金会](https
##
-### 状态👀
+### 项目状态
<hr>
-:white_check_mark: Version 5.5.2: 已发布 :tada:
+:white_check_mark: **Version 5.5.3-SNAPSHOT**: 正在积极开发中 :tada:
-🔗 请访问
[发布说明](https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md)
获得更详细的信息.
+🔗 请访问
[发布说明](https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md)
获得更详细的信息。
-:soon: Version 5.5.3
+:soon: **Version 5.5.3**
-我们目前正在开发 5.5.3 里程碑。
-请访问[里程碑](https://github.com/apache/shardingsphere/milestones) 获取最新信息。
+我们目前正在开发 5.5.3 版本，包含多项安全增强和性能优化。
+请访问[里程碑](https://github.com/apache/shardingsphere/milestones) 获取最新开发进展。
##
-### 工作原理
+### 技术架构演进
<hr>
-Apache ShardingSphere 由 JDBC、Proxy 这 2 款既能够独立部署，又支持混合部署配合使用的产品组成。
-它们均提供标准化的数据水平扩展、分布式事务和分布式治理等功能，可适用于如 Java 同构、异构语言、云原生等各种多样化的应用场景。
+Apache ShardingSphere 采用微内核 + 三层可插拔架构，实现了内核、功能组件与生态对接的完全解耦，为开发者提供了极致的灵活性和扩展能力。
+
+#### 微内核 + 三层可插拔模型
+
+**核心层**：
+- 查询优化器：智能 SQL 路由和执行计划优化
+- 分布式事务：ACID 事务保证和一致性协调
+- 执行引擎：高效的分布式执行和结果聚合
+
+**功能层**：
+- 数据分片、读写分离、联邦查询
+- 数据加密、数据脱敏、SQL 审计
+- 影子库、可观测性、流量控制
+
+**生态层**：
+- 数据库协议适配（MySQL、PostgreSQL、Firebird 等）
+- 注册中心集成（ZooKeeper、ETCD 等）
+- 配置管理、服务发现、监控集成
+
+#### 技术创新亮点
+
+**完全解耦架构**：
+- 数据库类型完全解耦，支持新数据库快速接入
+- 功能模块完全解耦，支持功能按需组合
+
+Apache ShardingSphere 由 JDBC、Proxy 两个既可独立部署又可混合部署的接入端组成，为 Java
同构、异构语言、云原生等多样化应用场景提供统一的分布式数据库解决方案。
### ShardingSphere-JDBC
@@ -180,17 +251,34 @@ Apache ShardingSphere 是多接入端共同组成的生态圈。
##
-### 解决方案
+### 核心功能矩阵
<hr>
-| *解决方案/功能* | *分布式数据库* | *数据安全* | *数据库网关* | *全链路压测* |
-|-----------|----------|---------------|----------------|---------|
-| | 数据分片 | 数据加密 | 异构数据库支持 | 影子库 |
-| | 读写分离 | 行级权限（TODO） | SQL 方言转换（TODO） | 可观测性 |
-| | 分布式事务 | SQL 审计（TODO） | | |
-| | 弹性伸缩 | SQL 防火墙（TODO） | | |
-| | 高可用 | | | |
+#### 分布式数据库核心能力
+- **数据分片**：水平分片、垂直分片、自定义分片策略、自动分片路由
+- **读写分离**：主从复制、负载均衡、故障转移、读权重配置
+- **分布式事务**：XA 事务、柔性事务、Seata AT 集成、事务传播
+
+#### 数据安全与治理
+- **数据加密**：字段级加密、透明加密、密钥管理、加密算法支持
+- **数据脱敏**：敏感数据保护、脱敏策略定制、动态脱敏规则
+- **权限控制**：细粒度权限、访问控制、安全策略
+
+#### 数据库网关能力
+- **异构数据库**：MySQL、PostgreSQL、Oracle、SQL Server、Firebird 等
+- **SQL 方言转换**：跨数据库 SQL 兼容、方言适配、语法转换
+- **协议适配**：数据库协议转换、多协议支持、通信优化
+
+#### 全链路压测与可观测性
+- **影子库**：压测数据隔离、环境分离、真实数据模拟
+- **可观测性**：性能监控、链路追踪、服务质量分析、指标采集
+- **流量分析**：SQL 性能分析、流量统计、瓶颈识别
+
+#### 企业级特性
+- **高可用**：集群部署、故障恢复、服务发现、健康检查
+- **云原生**：容器化部署、Kubernetes 集成、原生镜像支持
+- **监控告警**：实时监控、告警通知、性能指标、运维仪表盘
##
diff --git a/distribution/jdbc/pom.xml b/distribution/jdbc/pom.xml
index 27febce4836..1cc6d66ca09 100644
--- a/distribution/jdbc/pom.xml
+++ b/distribution/jdbc/pom.xml
@@ -180,7 +180,7 @@
</dependency>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
-
<artifactId>shardingsphere-infra-url-type-zookeeper</artifactId>
+ <artifactId>shardingsphere-infra-url-zookeeper</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
@@ -192,7 +192,7 @@
</dependency>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
- <artifactId>shardingsphere-infra-url-type-etcd</artifactId>
+ <artifactId>shardingsphere-infra-url-etcd</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
@@ -368,7 +368,7 @@
</dependency>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
-
<artifactId>shardingsphere-infra-url-type-zookeeper</artifactId>
+ <artifactId>shardingsphere-infra-url-zookeeper</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
@@ -381,7 +381,7 @@
</dependency>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
- <artifactId>shardingsphere-infra-url-type-etcd</artifactId>
+ <artifactId>shardingsphere-infra-url-etcd</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
@@ -668,7 +668,7 @@
</dependency>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
-
<artifactId>shardingsphere-infra-url-type-zookeeper</artifactId>
+ <artifactId>shardingsphere-infra-url-zookeeper</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
@@ -685,7 +685,7 @@
</dependency>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
- <artifactId>shardingsphere-infra-url-type-etcd</artifactId>
+ <artifactId>shardingsphere-infra-url-etcd</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
</dependency>
diff --git a/infra/url/type/etcd/pom.xml b/infra/url/type/etcd/pom.xml
index 859464f1275..d94c2fa42af 100644
--- a/infra/url/type/etcd/pom.xml
+++ b/infra/url/type/etcd/pom.xml
@@ -23,7 +23,7 @@
<artifactId>shardingsphere-infra-url-type</artifactId>
<version>5.5.3-SNAPSHOT</version>
</parent>
- <artifactId>shardingsphere-infra-url-type-etcd</artifactId>
+ <artifactId>shardingsphere-infra-url-etcd</artifactId>
<name>${project.artifactId}</name>
<dependencies>
diff --git a/infra/url/type/zookeeper/pom.xml b/infra/url/type/zookeeper/pom.xml
index 621b6835a4e..08d725073a4 100644
--- a/infra/url/type/zookeeper/pom.xml
+++ b/infra/url/type/zookeeper/pom.xml
@@ -23,7 +23,7 @@
<artifactId>shardingsphere-infra-url-type</artifactId>
<version>5.5.3-SNAPSHOT</version>
</parent>
- <artifactId>shardingsphere-infra-url-type-zookeeper</artifactId>
+ <artifactId>shardingsphere-infra-url-zookeeper</artifactId>
<name>${project.artifactId}</name>
<dependencies>
