-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[server] Add request based store properties endpoint to server #1374
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…stem store for forward compatibility support
15d22e6
to
3b2064f
Compare
xunyin8
reviewed
Dec 10, 2024
...src/integrationTest/java/com/linkedin/venice/endToEnd/TestServerStorePropertiesEndpoint.java
Outdated
Show resolved
Hide resolved
...src/integrationTest/java/com/linkedin/venice/endToEnd/TestServerStorePropertiesEndpoint.java
Outdated
Show resolved
Hide resolved
...src/integrationTest/java/com/linkedin/venice/endToEnd/TestServerStorePropertiesEndpoint.java
Show resolved
Hide resolved
...s/venice-server/src/main/java/com/linkedin/venice/listener/ServerReadMetadataRepository.java
Outdated
Show resolved
Hide resolved
...s/venice-server/src/main/java/com/linkedin/venice/listener/ServerReadMetadataRepository.java
Outdated
Show resolved
Hide resolved
xunyin8
reviewed
Dec 10, 2024
.../src/main/resources/avro/StorePropertiesResponseRecord/v1/StorePropertiesResponseRecord.avsc
Show resolved
Hide resolved
xunyin8
reviewed
Dec 10, 2024
internal/venice-common/src/main/java/com/linkedin/venice/meta/ReadOnlyStore.java
Outdated
Show resolved
Hide resolved
Update fork
Update fork
xunyin8
approved these changes
Jan 7, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
This was referenced Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[server] Add request based store properties endpoint to server
Add endpoint to server to allow DVC to retrieve store metadata, bypassing the store based metadata retrieval. This change will not impact any behavior of the DVC during deployment. It will only add the option for the DVC to use the metadata via the endpoint. A future PR will make changes to the DVC to utilize this endpoint.
Endpoint Details
Method: GET
Path:
/store_properties/{store_name}
Example Response
How was this PR tested?
Unit and Integration test included in PR.
Does this PR introduce any user-facing changes?