infra.url.ShardingSphereURLLoader from being manually converted to YAML from files such as XML or JSON. After parsing and loading the YAML file into ShardingSphere’s metadata, the next behavior will be Native Build Tools shall prevail. Due to the limitations of Gradle 8.6, users need to introduce the JSON file of Metadata Repository through Maven dependency. Reference https: //github.com/graalvm/nati following content to src/main/resources/META-INF/native-image/ exmaple-test-metadata/reflect-config.json to used normally under GraalVM Native Image. [ { "name":"org.example.test.TestShardingAlgorithmFixture"

1 作为 YAML 的编写规范，这并不阻止 org.apache.shardingsphere.infra.url. ShardingSphereURLLoader 的自定义实现从 XML 或 JSON 等文件手动转化为 YAML。 在解析并加载 YAML 文件为 ShardingSphere 的元数据后，会再次通过模式配置的相关配置决定下一步 行为。讨论两种情况， 1. 元数据持久化仓库中不存在 Tasks，以 GraalVM Native Build Tools 的文档为准。由于 Gradle 8.6 的限制，用户需要通过 Maven 依赖的形式引入 Metadata Repository 的 JSON 文件。参考 https://github.com/graalvm/native‐build‐too ls/issues/572 。 plugins { id 'org.graalvm.buildtools TestShardingAlgorithmFixture 在 src/main/resources/META-INF/native-image/exmaple-test-metadata/ reflect-config.json 加入如下内容即可在正常在 GraalVM Native Image 下使用。 [ { "name":"org.example.test.TestShardingAlgorithmFixture"

following content to src/main/resources/META-INF/native-image/ exmaple-test-metadata/reflect-config.json to used normally under GraalVM Native Image. [ { "name":"org.example.test.TestShardingAlgorithmFixture" handled with the following bash command. Contributors may still need to manually adjust specific JSON entries and GraalVM Tracing Agent Filter chain of Maven Profile. The following command is only an native:metadata-copy 9.1. ShardingSphere-JDBC 142 Apache ShardingSphere document Please manually delete JSON files without any specific entries. 9.2 ShardingSphere-Proxy Configuration is the only module in

information is transmitted in the form of Header, the key is shardingContext, and the value is in json format. public class HttpJobMain { public static void main(String[] args) { new ScheduleJobBootstrap(regCenter

TestShardingAlgorithmFixture 在 src/main/resources/META-INF/native-image/exmaple-test-metadata/ reflect-config.json 加入如下内容即可在正常在 GraalVM Native Image 下使用。 [ { "name":"org.example.test.TestShardingAlgorithmFixture" Agent 执行单元测试，并在特定目录下生成或合并已有的 GraalVM Reachability Meta‐ data 文件。可通过如下 bash 命令简单处理此流程。贡献者仍可能需要手动调整具体的 JSON 条目，并在 适当的时候调整 Maven Profile 和 GraalVM Tracing Agent 的 Filter 链。 以 下 命 令 仅 为 shardingsphere-test-native /mvnw -PgenerateMetadata -DskipNativeTests -e -T1C clean test native:metadata-copy 请手动删除无任何具体条目的 JSON 文件。 9.2 ShardingSphere-Proxy 配置是 ShardingSphere‐Proxy 中唯一与开发者交互的模块，通过它可以快速清晰的理解 ShardingSphere‐

可通过属性配置 http.url,http.method,http.data 等配置待请求的 http 信息。分片信息以 Header 形式传递，key 为 shardingContext，值为 json 格式。 public class HttpJobMain { public static void main(String[] args) { new ScheduleJobBootstrap(regCenter

0.0-beta curl -X POST \ http://localhost:8888/scaling/job/start \ -H 'content-type: application/json' \ -d '{ "ruleConfig": { "source": { "type": "shardingSphereJdbc", "parameter": " dataSources:

shardingSphereJdbc 示例： curl -X POST \ http://localhost:8888/scaling/job/start \ -H 'content-type: application/json' \ -d '{ "ruleConfig": { "source": { "type": "shardingSphereJdbc", "parameter": " 4.4. ShardingSphere-Scaling