[FEATURE] Why gravitino store schema and table propertites?
Open
question
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 935
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 315
Description
### Describe the feature
I can understand why gravitino store metalake and catalogs,but i cant understand why gravitino store schema and table propertites。because I don‘t find any place useing it out of audit。Is this to prepare for other future needs?
### Motivation
_No response_
### Describe the solution
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reviewing the existing metalake, catalog, schema, and table property handling, including the audit usage mentioned in the issue. Done would require a maintainer decision or clarification of whether these properties serve future needs; the issue names no files, tests, or concrete change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100