Skip to content

DOCS: Improve Documentation on Write Support #1008

Open
Username46786/iceberg
#3

Description

@sungwy

Feature Request / Improvement

We currently have Write support through two modes:

  1. through the Table API
  2. through the Transaction API

We also have support for different modes of writes like:

  1. append
  2. overwrite
  3. delete

Which make use of different arg parameters.

It would be great to update our docs to describe each of these operations and API modes explicitly in detail as separate subsections, and pad in any missing details (like the use of overwrite_filter in overwrite)

Activity

  1. guitcastro commented on Aug 7, 2024

    @guitcastro
    Contributor

    @sungwy When using overwrite how can we compare fields between source and target? like:

      source.id = target.id and source.updated < target.updated
    
  2. kevinjqliu commented on Aug 9, 2024

    @kevinjqliu
    Contributor

    someone asked about merge/upserts use cases in the slack channel as well, similar to overwrite_filter

  3. kevinjqliu commented on Aug 13, 2024

    @kevinjqliu
    Contributor
  4. iamvyshnavi commented on Feb 5, 2025

    @iamvyshnavi

    Hi, I am new to open source and would love to contribute to this issue. Can I work on this?

  5. shrutisachan08 commented on Feb 6, 2025

    @shrutisachan08

    Hii, I would like to work on this. I can update documentation by adding separate subsections for each write mode(append, overwrite, delete). I can insert some examples like including about overwrite_filter usage. Please let me know if there are any formatting details you would like me to include. Please assign me this issue.

  6. github-actions commented on Aug 6, 2025

    @github-actions

    This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

  7. pramila-bishnoi commented on Nov 15, 2025

    @pramila-bishnoi

    Hi! I am new to contributing to PyIceberg and would like to pick up this documentation task to add sections for append, overwrite, and upsert functionality as mentioned by the previous contributors. I will start setting up my environment now. Please consider assigning this to me.

  8. pramila-bishnoi commented on Nov 16, 2025

    @pramila-bishnoi

    Hi ,

    I had asked earlier about taking on this documentation issue but didn't hear back, so I went ahead and completed the main task to keep things moving.

    The core documentation (adding all write operations to api.md) is now finished.

    api.md

    (attached file)

    I included the full documentation blocks for overwrite(), delete(), dynamic_partition_overwrite(), upsert(), and the Transaction API.

    Could you please review the changes I made in the attached api.md file? I want to make sure the content is correct before proceeding.

    Proposed Final Change:- I haven't done this yet, but I recommend adding cross-links from the headings (like append()) to the relevant Python API reference documentation. This greatly improves user experience and navigation.

    Should I add these cross-links??

    Is there anything else you think I should add or change in the file?

    Once confirmed, i'll create a new branch, and open a formal PR.

    Thanks !

  9. pramila-bishnoi commented on Nov 16, 2025

    @pramila-bishnoi
  10. kevinjqliu commented on Nov 18, 2025

    @kevinjqliu
    Contributor

    hey @pramila-bishnoi feel free to open a PR so its easier to review the changes.

  11. pramila-bishnoi commented on Nov 23, 2025

    @pramila-bishnoi

    Hi @kevinjqliu , just checking in on this PR. Is there anything else I can provide on my end, or any ETA on when it might be reviewed? Thanks!

  12. github-actions commented on Jun 13, 2026

    @github-actions

    This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

  13. Zhuoxi2000 commented on Jul 10, 2026

    @Zhuoxi2000

    Opened #3647 restructuring the write docs into per-operation subsections + documenting the Transaction write mode

  14. iSparshP commented on Aug 18, 2026

    @iSparshP

    Hi, I would like to pick this up.
    Looks like #3647 took a run at this, but got auto-closed by the stale bot for inactivity, so I don't think anyone's actively on it right now. @Zhuoxi2000 @pramila-bishnoi if either of you is still working on it let me know, otherwise happy to take it forward.

    I am going to document the Table API and Transaction API write paths as separate subsections, cover append / overwrite / delete under each, and fill in overwrite_filter since that's the one that's underdocumented today. I will reuse the structure from #3647 where it holds up and open a PR for review.

  15. pramila-bishnoi commented on Aug 18, 2026

    @pramila-bishnoi

    Hi @iSparshP, I was working on this earlier and had opened PR #2770, but it wasn't reviewed and was eventually closed due to inactivity. I'm not actively working on it anymore, so please feel free to take it forward. Thanks!

  16. iSparshP commented on Aug 19, 2026

    @iSparshP

    Thanks @pramila-bishnoi, appreciate the handoff. I will go through #2770 and #3647 to reuse what's already there and build on top. Will open a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions