fix: use request id to locate the correct cache entry to update #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What type of PR is this?
fix: use request id to locate the correct cache entry to update
What this PR does / why we need it:
The major change:
Other changes:
request_idto Milvus storage.insertoperation withupsertinMilvusCache.addEntry. Previously, it always inserted two entries into storage—one forAddPendingRequestand another forUpdateWithResponse. Now, it updates the entry if a cache entry with the samerequest_idalready exists.UpdateWithResponse. I think it's not useful because we this unknown cache entry doesn't havemodelfield.pendingRequestsandpendingRequestsLocksince they are no longer in use.milvus.mkto enable starting Attu (the Milvus UI), which is helpful for browsing data.Which issue(s) this PR fixes:
Fixes #144
Release Notes: Yes/No