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

[EPIC] Catalog capability framework #2952

Closed
6 tasks done
mchades opened this issue Apr 15, 2024 · 0 comments
Closed
6 tasks done

[EPIC] Catalog capability framework #2952

mchades opened this issue Apr 15, 2024 · 0 comments
Assignees
Labels
epic Key feature

Comments

@mchades
Copy link
Contributor

mchades commented Apr 15, 2024

Describe the proposal

Currently, we lack catalog-level capability management, which results in the need to duplicate some validation work across different catalogs.

Task list

@mchades mchades added the epic Key feature label Apr 15, 2024
@mchades mchades self-assigned this Apr 15, 2024
@mchades mchades added this to the Gravitino 0.5.0 milestone Apr 15, 2024
jerryshao pushed a commit that referenced this issue Apr 20, 2024
### What changes were proposed in this pull request?

 - add name spec for entity name

### Why are the changes needed?

Fix: #2952

### Does this PR introduce _any_ user-facing change?

yes, have more limitation in name now

### How was this patch tested?

added tests
diqiu50 pushed a commit to diqiu50/gravitino that referenced this issue Jun 13, 2024
### What changes were proposed in this pull request?

 - add name spec for entity name

### Why are the changes needed?

Fix: apache#2952

### Does this PR introduce _any_ user-facing change?

yes, have more limitation in name now

### How was this patch tested?

added tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Key feature
Projects
None yet
Development

No branches or pull requests

1 participant