Skip to content
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

feat: add parent() method to kvapi::Key to describe the hierarchical structure of meta-service data #14716

Merged
merged 1 commit into from Feb 23, 2024

Conversation

drmingdrmer
Copy link
Member

@drmingdrmer drmingdrmer commented Feb 22, 2024

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

feat: add parent() method to kvapi::Key to describe the hierarchical structure of meta-service data

Keys in meta-service have hierarchical structure.
For example a database is the parent of a table.

The kvapi::Key should expose a structure that enables the traversal
from a Tenant to all associated data when exporting metadata for that
tenant.

Changelog

  • New Feature

Related Issues


This change is Reviewable

@github-actions github-actions bot added the pr-feature this PR introduces a new feature to the codebase label Feb 22, 2024
…l structure of meta-service data

Keys in meta-service have hierarchical structure.
For example a database is the parent of a table.

The `kvapi::Key` should expose a structure that enables the traversal
from a `Tenant` to all associated data when exporting metadata for that
tenant.
@drmingdrmer drmingdrmer marked this pull request as ready for review February 23, 2024 02:41
@drmingdrmer drmingdrmer merged commit 5d06510 into datafuselabs:main Feb 23, 2024
73 of 74 checks passed
@drmingdrmer drmingdrmer deleted the 31-kvapi-key-parent branch February 23, 2024 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-feature this PR introduces a new feature to the codebase
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant