youngkermit8-coder opened a new pull request, #2383: URL: https://github.com/apache/rocketmq-dashboard/pull/2383
## Summary - enforce NameServer registry name uniqueness in the database schema - return HTTP 409 for both precheck and database-detected create/update conflicts - add service regressions for concurrent loser paths and schema integration coverage ## Root cause and impact The service used a `selectCount` duplicate check before writes, while `rmq_nameserver` had no unique constraint on `name`. Concurrent creates or renames could both pass the precheck and persist duplicate registry names. This change makes the database the source of truth with a unique key and translates the resulting `DuplicateKeyException` into the same stable conflict response used by the precheck. ## Validation - the two new service regressions failed on the unmodified base because the raw `DuplicateKeyException` escaped - focused NameServer service, controller, and schema tests: 27 passed - full Maven test suite: 1357 passed, 0 failed - Checkstyle: 0 violations - `git diff --check`: passed Fixes #2382 -- 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]
