apache / apache/iceberg

Iceberg proto representations of tech spec

Open
#16,195 0 comments 0 reactions 0 assignees View on GitHub
improvement
Dominant language
Java
Stars
9.2k
Forks
3.5k
Avg merge
2d 16h
Merged PRs (30d)
129

Description

### Feature Request / Improvement

Hi team,
quick thought on the tech spec: would it make sense to add an Iceberg proto module? We recently did a POC and found that this really solves the pain points of building a client-server app on top of the Iceberg REST catalog. It gives us a solid data model for client-server communication, and it makes managing and switching between Iceberg spec versions much easier. Let me know what you think!

### Query engine

None

### Willingness to contribute

- [x] I can contribute this improvement/feature independently
- [x] I would be willing to contribute this improvement/feature with guidance from the Iceberg community
- [ ] I cannot contribute this improvement/feature at this time

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by reviewing the Iceberg REST catalog and the tech-spec version requirements; clarify the proto module's supported representations and client-server scope with the community. Done means an agreed module design that handles the intended spec versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.