[#6814] feat(core): Support update aliases for model version.
What changes were proposed in this pull request?
Support update aliases for model version.
- [X] PR1: Add ModelVersionChange API interface, Implement the update alias logic in model catalog and JDBC backend logic, update related event.
- [ ] PR2: Add REST endpoint to support model version change, add Java client and Python client for model version alias update.
Why are the changes needed?
Fix: #6814
Does this PR introduce any user-facing change?
no.
How was this patch tested?
local test. When an alias is updated, all old aliases are removed and all new aliases are inserted, keeping the version number unchanged
Hi @jerryshao , could you please review this PR when you have time? I’d really appreciate your feedback.
Hi @jerryshao , I've completed the code updates and would appreciate your review of the PR when you have a moment. Here's a summary of the commits:
- Refactor the
UpdateAliasclass.
Can you please also update the doc in this PR?
Can you please also update the doc in this PR?
@jerryshao Personally, I think it is appropriate to add in the next PR, this PR has not added the request related content.
Hi @jerryshao , I've completed the code updates and would appreciate your review of the PR when you have a moment. Here's a summary of the commits:
- Add new test cases
- Fix typo issues.
Hi @jerryshao , I've completed the code updates and would appreciate your review of the PR when you have a moment. Here's a summary of the commits:
- Fix NPE in static method of
ModelVersionChange.updateAliases() - Fix handle logic of
ModelVersionChange.updateAliases(), If use remove and add the same alias, nothing happens.
Generally LGTM, just one issue need to be fixed. @Abyss-lord
Hi @jerryshao , I've completed the code updates and would appreciate your review of the PR when you have a moment. Here's a summary of the commits:
- Move Duplicate removal logic in server side.
The first part is done, please do the followup things.