rishi-rana commented on PR #39882:
URL: https://github.com/apache/shardingsphere/pull/39882#issuecomment-5755095485
The failing check `E2E - SQL (Stage 2) (proxy, Cluster, MySQL,
db_tbl_sql_federation)` appears unrelated to this PR.
All 28 errors are in `GeneralDQLE2EIT` and report the same cause:
```
java.sql.SQLSyntaxErrorException: Unsupported SQL operation: MySQL BIN
function
```
`BIN` was added to the unsupported list in
`MySQLSQLFederationFunctionRegister` by f1cb20ba4e9 ("Mark remaining MySQL
functions unsupported in SQL Federation", #39910), while
`test/e2e/sql/src/test/resources/cases/dql/cases/db_tbl_sql_federation/e2e-dql-select-for-db-tbl-sql-federation.xml`
on master still contains 10 assertions that call `bin(...)`. The E2E cases and
the function registration look inconsistent with each other on current master.
Why this looks external to the PR:
- This branch contains no change under `test/e2e/sql`, and no change to SQL
Federation or function registration.
- The branch tip `3c86b0011aed3d8a4b0b8e52baad4b5dd1fed6bd` does not contain
f1cb20ba4e9, yet the job fails with an error that commit introduced, so the job
ran the pull request merge ref rather than the branch alone.
- Every failing assertion is federation function resolution; no transaction,
DDL or meta data refresh frame appears in the stacks.
The transaction E2E legs that exercise this change are passing on all three
database images.
I have not reproduced the federation suite locally, so please treat this as
an observation rather than a diagnosis of #39910. Happy to raise it separately
if that is the better place for it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
