The GitHub Actions job "E2E - SQL" on shardingsphere.git/fix/39537-column-offset has failed. Run started by GitHub user fudianchn (triggered by fudianchn).
Head commit for run: fda5944d76fc2348a68ef3c411db723f0b67d5fe / 付典 <[email protected]> Fix wrong column labels and count when metadata drifts from backend schema For queries on rule-enhanced tables, column count, names, labels and the label-index map were derived from projections expanded against ShardingSphere metadata, then paired positionally with actual backend rows. After out-of-band DDL on the backend, the metadata view drifts from the live schema and clients silently receive values attributed to wrong columns. The backend result set metadata truthfully describes the actual rows, so use the projection-derived view only when its column count matches the actual result set metadata; otherwise the result set metadata is authoritative. QueryHeaderBuilderEngine now delegates to ShardingSphereResultSetMetaData instead of duplicating the projection lookup, and StandardDatabaseProxyConnector derives the header count from the same source. Fixes #39537. Signed-off-by: 付典 <[email protected]> Report URL: https://github.com/apache/shardingsphere/actions/runs/33043613504 With regards, GitHub Actions via GitBox
