-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
The "Status" paragraph in the readme seems very outdated #9127
Comments
Hey @ronkorving Thanks for raising this. That's very true, the status page seems to be very outdated. The V1, and V2 specs are out there, and work is being done on the V3 spec (more type promotions, nanosecond support, and more). Are you interested in trimming down the section, and updating it where needed? |
@Fokko Thanks for the engagement :) |
Yes, I think that makes a lot of sense. @bitsondatadev is also working on updating the roadmap, it might be a good idea to link to that so we have one single place where people can see what's going on 👍 |
@ronkorving Let me know if you'd like to raise the PR, or I can do it as well. For now pointing to the roadmap page will be the best. Eventually, I'd like there to be something less static that exists directly in GitHub for this. A main project board or possibly a wiki with links to individual projects. |
I would be happy to make my first contribution :) |
PR is ready for review ^ |
Apache Iceberg version
None
Query engine
None
Please describe the bug 🐞
Looking at the ReadMe in the root of this repository, one would be mistaken for thinking we're living in Table v1 times.
Quote start:
Iceberg is under active development at the Apache Software Foundation.
The core Java library that tracks table snapshots and metadata is complete, but still evolving. Current work is focused on adding row-level deletes and upserts, and integration work with new engines like Flink and Hive.
The Iceberg format specification is being actively updated and is open for comment. Until the specification is complete and released, it carries no compatibility guarantees. The spec is currently evolving as the Java reference implementation changes.
Java API javadocs are available for the main.
Quote end
That last sentence seems incomplete. But more importantly, I think the information provided is, today at least, no longer correct. I've been told there are compatibility guarantees, and what's being worked on today is probably no longer row-level deletes and upserts.
I would like to suggest that an update, or perhaps a slimming down of the text, is overdue.
The text was updated successfully, but these errors were encountered: