sunnysabor commented on PR #7408: URL: https://github.com/apache/shenyu/pull/7408#issuecomment-5939265897
I traced the 32 `AdminQueryIndexTest` failures as a schema parity gap: these assertions were added with #7238 and are currently defined in H2/MySQL initialization (and MySQL upgrade DDL), while PostgreSQL initialization contains only `idx_meta_data_namespace_path` from that set. The new matrix is therefore surfacing that query-index coverage does not yet extend to the other tested dialects. For the dialect rollout, should I carry the #7238 index definitions into the PostgreSQL/openGauss/Oracle initialization and upgrade scripts, preserving Oracle identifier constraints, or would maintainers prefer those assertions to remain limited to H2/MySQL? My preference is to keep the full dialect checks and add the equivalent indexes so query performance does not vary by supported backend. -- 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]
