Skip to content
View ym0506's full-sized avatar
  • South Korea
  • 12:36 (UTC +09:00)

Block or report ym0506

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ym0506/README.md

한국어

Apache ShardingSphere

7 SQL execution and compatibility improvements · 11 merged PRs

Index-name compatibility across DDL, metadata, and pipeline · #38449
Fixed generated names exceeding database limits and restored logical-name recovery across SQL rewriting, metadata refresh, and pipeline paths. Preserved existing names that fit. Scope: 36 files, including tests.

Same value, different shard · Opt-in routing feature · #38327
Added HASH_MOD normalization so equal signed 32-bit integer values route consistently across Integer, Long, and BigInteger. Kept legacy routing as the default for upgrade compatibility.

Missing failure notification before compatibility fallback · Reliability fix · Issue #39763Merged PR #39764
While auditing execution hooks for RouteContract, fixed a missing SQL failure notification before a compatibility fallback. Regression tests verify preserved return values and exactly one failure notification in trunk and worker paths.

All 11 PRs and design decisions

OpenTelemetry Java instrumentation

JDBC SQL masking settings now respected · #20020 — merged

Made SQL recorded in JDBC spans follow the configured masking settings while preserving query results. Updated OpenTelemetryDriver and shared DB configuration; 16 new H2 regression cases cover Statement and PreparedStatement.

Implementation, tests, and maintainer review

RouteContract

Java library author · v0.1.4 on Maven Central

Detects execution changes that result assertions miss. In a controlled MySQL example, the query result stays unchanged while observed JDBC execution attempts increase 1 → 2. RouteContract rejects the change against a reviewed baseline in CI.

Checks execution budgets, data sources, and rewritten SQL; generates Markdown/JSON review reports. The public release was verified across Java 17/21 × Gradle/Maven.

Run the MySQL demo · Install · Tests and isolated experiments

Scope: ShardingSphere-JDBC 5.5.3; synchronous, non-batch PreparedStatement. Counts are hook-observed attempts.


All 13 merged upstream PRs across 3 projects · Email

Contribution and release status checked: 2026-09-14.

Pinned Loading

  1. routecontract routecontract Public

    CI checks for ShardingSphere-JDBC execution changes, even when query results stay the same. Java 17/21 · ShardingSphere-JDBC 5.5.3.

    Java 2

  2. apache/shardingsphere apache/shardingsphere Public

    Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.

    Java 20.8k 6.9k

  3. open-telemetry/opentelemetry-java-instrumentation open-telemetry/opentelemetry-java-instrumentation Public

    OpenTelemetry auto-instrumentation and instrumentation libraries for Java

    Java 2.6k 1.2k