-
Notifications
You must be signed in to change notification settings - Fork 53
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
Nessie REST API Support for Namespace Operations #297
base: main
Are you sure you want to change the base?
Conversation
type namespaceItem struct { | ||
Type string `json:"type"` | ||
ID string `json:"id"` | ||
Elements []string `json:"elements"` | ||
} |
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.
is this something in the actual REST API spec? or is it unique to Nessie's implementation? If this is unique to Nessie, then I would not be in favor of adding this to the REST catalog implementation
type payload struct { | ||
Remove []string `json:"removals"` | ||
Updates iceberg.Properties `json:"updates"` | ||
PropertyUpdates iceberg.Properties `json:"propertyUpdates"` | ||
PropertyRemovals []string `json:"propertyRemovals,omitempty"` | ||
} |
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.
Isn't this change incompatible with the REST API?
Overview
This PR adds support for using Apache Nessie as a REST catalog by implementing the Nessie API paths for namespace operations. The changes ensure compatibility with Nessie API v0.102.4.
Changes
Modified
catalog/rest.go
Updated namespace-related functions to align with Nessie API paths:
Added
context.go
GetRefFromContext
andWithRef
functions to handle reference passing through contextTesting
I had to modify path and structure of test cases to make it work with nessie
All Test Cases are passing