. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Background Information Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Build GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 166 Use Helm . . . . . . . . . . 3.9 Sharding In addition to internal distributed primary key, does ShardingSphere support other native auto‐increment keys? . . . . . . . . . . . . . . . . . . . . 580 13.4 Single table . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 v Background Information Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Build GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 147 Use Helm . . . . . . . . . . 4.9 Sharding In addition to internal distributed primary key, does ShardingSphere support other native auto‐increment keys? . . . . . . . . . . . . . . . . . . . . 551 13.5 DistSQL . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 背景信息 . . . . . . . . . Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 构建 GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 152 使用 Helm . . . . . . . . . . 配置 useOriginalSQLWhenTranslatingFailed 参数，是否在 SQL 翻译失败后使用原始 SQL 继续执行 配置示例 sqlTranslator: type: Native useOriginalSQLWhenTranslatingFailed: true 相关参考 • JAVA API：SQL 翻译 混合规则 背景信息 ShardingSphere

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 9.1.7 GraalVM Native Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 背景信息 . . . . . . . . . Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 构建 GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 133 使用 Helm . . . . . . . . . . ShardingSphere 中。 9.1.5 不支持项 DataSource 接口 • 不支持 timeout 相关操作。 Connection 接口 • 不支持存储过程，函数，游标的操作； • 不支持执行 native SQL； • 不支持 savepoint 相关操作； • 不支持 Schema/Catalog 的操作； • 不支持自定义类型映射。 Statement 和 PreparedStatement

Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 构建 GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 126 可观察性 . . . . . . . . . . . . 翻译器 9.1.5 不支持项 DataSource 接口 • 不支持 timeout 相关操作。 Connection 接口 • 不支持存储过程，函数，游标的操作； • 不支持执行 native SQL； • 不支持 savepoint 相关操作； • 不支持 Schema/Catalog 的操作； • 不支持自定义类型映射。 Statement 和 PreparedStatement 构建 GraalVM Native Image(Alpha) 背景信息 本节主要介绍如何通过 GraalVM 的 native-image 组件构建 ShardingSphere‐Proxy 的 Native Image 和对应的 Docker Image 。 注意事项 • ShardingSphere Proxy 尚未准备好与 GraalVM Native Image 集成。其在 https://github

Docker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Build GraalVM Native Image(Alpha) . . . . . . . . . . . . . . . . . . . . . . . . . 185 Use Helm . . . . . . . . . . 3.9 Sharding In addition to internal distributed primary key, does ShardingSphere support other native auto‐increment keys? . . . . . . . . . . . . . . . . . . . . 498 8.4 Encryption . . . . . . . . HA of your distributed database cluster with ShardingSphere’s Operator on Ku‐ bernetes, and the native HA of your existing data sources. Data Mi‐ gra‐ tion Data migration is the key to connecting

applicable in a variety of situa‐ tions such as Java isomorphism, heterogeneous language and cloud native. Apache ShardingSphere aiming at reasonably making full use of the computation and storage capacity protocol. 1.1.3 ShardingSphere-Sidecar(TODO) ShardingSphere‐Sidecar (TODO) defines itself as a cloud native database agent of the Kubernetes en‐ vironment, in charge of all the access to the database in the create ShardingSphere- DataSource, which implements DataSource interface of JDBC. It can be used for native JDBC or JPA, MyBatis and other ORM frameworks. DataSource dataSource = ShardingSphereDataSourceFactory

3.9 Sharding In addition to internal distributed primary key, does ShardingSphere support other native auto‐increment keys? . . . . . . . . . . . . . . . . . . . . 459 8.4 Encryption . . . . . . . . 1.3 Advantages • Ultimate Performance Having been polished for years, the driver is close to a native JDBC in terms of efficiency, with ultimate performance. • Ecosystem Compatibility The proxy can engine It can further provide distributed capabilities and traffic enhancement functions based on native database capabilities. The former can break through the bottleneck of the underlying database in

[Sharding] In addition to internal distributed primary key, does Sharding‐ Sphere support other native auto‐increment keys? . . . . . . . . . . . . . . . . 307 7.7.16 16. [Encryption] How to solve that applicable in a variety of situations such as Java isomorphism, heterogeneous language and Cloud‐Native. As the cornerstone of enterprises, the relational database has a huge market share. Therefore, protocol. 1.1.3 ShardingSphere-Sidecar(TODO) ShardingSphere‐Sidecar (TODO) defines itself as a cloud‐native database agent of the Kubernetes envi‐ ronment, in charge of all database access in the form of

16 [Sharding] In addition to internal distributed primary key, does ShardingSphere support other native auto‐increment keys? . . . . . . . . . . . . . . . . . . . . 350 7.8.17 [Encryption] How to solve applicable in a variety of situations such as Java isomorphism, heterogeneous language and Cloud‐Native. As the cornerstone of enterprises, the relational database has a huge market share. Therefore, 1.1 1.1.3 ShardingSphere-Sidecar(TODO) ShardingSphere‐Sidecar (TODO) defines itself as a cloud‐native database agent of the Kubernetes envi‐ ronment, in charge of all database access in the form of