Docs: add newRowDelta and remove iceberg-hive3 reference in Java Iceberg API doc#13266
Docs: add newRowDelta and remove iceberg-hive3 reference in Java Iceberg API doc#13266krikera wants to merge 1 commit intoapache:mainfrom
Conversation
|
Hi, @manuzhang! Just checking in. Any feedback or changes needed for this PR? Thanks! |
|
@krikera Have you checked whether other information on this doc is up-to-date? |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
@krikera are you still working on this PR? |
| * `newRowDelta` -- used to insert, update, and delete rows atomically | ||
| * `newTransaction` -- create a new table-level transaction | ||
| * `rewriteManifests` -- rewrite manifest data by clustering files, for faster scan planning | ||
| * `rollback` -- rollback the table state to a specific snapshot |
There was a problem hiding this comment.
New APIs missing here
- updateStatistics
- updatePartitionStatistics
- expireSnapshots
- manageSnapshots
|
@manuzhang,I think this PR still requires some additions. Can I work on this? |
|
@ayushjariyal Since there's no reply from @krikera, you may open a new PR adding @krikera as a co-author. |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
3 participants
This PR updates the API documentation to fix two issues identified in [#13249]