Web UI V2: Column model does not support displaying or editing comment, nullable, autoIncrement, defaultValue
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 935
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 298
Description
### What would you like to be improved?
In Gravitino 1.2.1 Web UI V2, the Column model/table does not support displaying or managing the following basic column properties that are fully supported in Web UI V1:
column comment
nullable (is null allowed)
autoIncrement
defaultValue
The Columns table in V2 UI only shows:
Column Name
Data Type
Tags
Policies
All basic metadata attributes are missing, and there is NO entry to view or set them.
### How should we improve?
**To Reproduce**
1.Open Gravitino Web UI V2
2.Go to any Metalake → Catalog → Schema → Table
3.Open the table detail page and view the Columns section
4.Check column properties: only name and type are displayed
5.Try to find settings to show comment/nullable/autoIncrement/defaultValue: no such button/entry exists
**Expected behavior**
1.Web UI V2 should keep the same column metadata ability as V1:
2.Display column comment, nullable, autoIncrement, defaultValue in Columns table
3.Support column settings to toggle visible fields
4.Support viewing and editing these basic attributes
**Actual behavior**
1.No comment shown
2.No nullable indicator
3.No autoIncrement / defaultValue support
4.No column settings button to enable these fields
5.Basic column metadata management is broken
**Screenshots / Additional context**
1.Web UI V1 (works well): shows full column details including comment, nullable, type, etc.
2.Web UI V2 (broken): only shows Column Name + Data Type, no basic attributes at all
3.This issue strongly affects metadata management usability. Users cannot view or maintain complete column schema in V2 UI.
Contributor guide
Research direction
Start at the Web UI V2 table detail page's Columns section and compare it with the Web UI V1 column view, which the issue identifies as the working reference. Trace the column model and table controls to determine how comment, nullable, autoIncrement, and defaultValue are represented. Done means these attributes can be displayed, configured for visibility, and viewed or edited in V2.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100