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

[Subtask] use the capability of column default value #2953

Closed
Tracked by #2952
mchades opened this issue Apr 15, 2024 · 0 comments · Fixed by #2859
Closed
Tracked by #2952

[Subtask] use the capability of column default value #2953

mchades opened this issue Apr 15, 2024 · 0 comments · Fixed by #2859
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@mchades
Copy link
Contributor

mchades commented Apr 15, 2024

Describe the subtask

Since we introduce the capability framework, we should use the capability of column default value

Parent issue

#2952

@mchades mchades added the subtask Subtasks of umbrella issue label Apr 15, 2024
@mchades mchades added this to the Gravitino 0.5.0 milestone Apr 15, 2024
@mchades mchades self-assigned this Apr 15, 2024
jerryshao pushed a commit that referenced this issue Apr 16, 2024
### What changes were proposed in this pull request?

- remove the column default value validation in Hive catalog and Iceberg
catalog
- available column default capability in the framework

### Why are the changes needed?

Fix: #2953 

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

no

### How was this patch tested?

tests added
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subtask Subtasks of umbrella issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant