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.

Sign up for GitHub

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

Jump to bottom

[Subtask] refine drop metalake semantics and behavior #5154

Open
Tracked by #5031
mchades opened this issue Oct 16, 2024 · 0 comments · May be fixed by #5155
Open
Tracked by #5031

[Subtask] refine drop metalake semantics and behavior #5154

mchades opened this issue Oct 16, 2024 · 0 comments · May be fixed by #5155
Assignees
@mchades
Labels
subtask Subtasks of umbrella issue

Comments

@mchades
Copy link
Contributor

mchades commented Oct 16, 2024 •
edited
Loading

Describe the subtask

  • Add "in-use" as the property and set "true" as the default value for metalake.
  • Add "force" parameter to drop metalake API
  • Add "enableMetalake()" and "disableMetalake()" API for metalake
  • Check metalake in use before operate entities

Parent issue

#5031
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mchades mchades

Labels
subtask Subtasks of umbrella issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#5154] refactor(drop-metalake): re-define drop metalake mchades/gravitino
1 participant
@mchades