[REST API + KafkaSQL] Significant updates to the REST API to change how artifact and version metadata behave #4410
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.
/groups/:groupId/artifacts/:artifactId
now GETs and PUTs metadata, not content/groups/:groupId/artifacts/:artifactId/owner
endpoint - owner is now just another metadata propertyAll of these changes required multiple storage layer updates which are relatively easy in SQL but annoying in KafkaSQL. As a result, I have changed the KafkaSQL layer to use more of a 1-1 RPC style approach rather than the existing approach that is based on log compaction. This means we are now committed to implementing snapshotting.