Skip to content

Row-level-deletes in spec is not rendered as bulleted list #13813

Closed

Description

@manuzhang

Feature Request / Improvement

https://iceberg.apache.org/spec/#row-level-deletes

Image

Query engine

None

Willingness to contribute

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

Activity

  1. added
    improvementPR that improves existing functionality
    beginnerIssues for apache iceberg beginners, enjoy to contribute !
    on Aug 14, 2025
  2. JeonDaehong commented on Aug 14, 2025

    @JeonDaehong
    Contributor

    Can I work on this PR?

  3. manuzhang commented on Aug 14, 2025

    @manuzhang
    MemberAuthor

    Yes, feel free to open a PR.

  4. JeonDaehong commented on Aug 18, 2025

    @JeonDaehong
    Contributor

    @manuzhang

    I have created and submitted the PR.

    I would appreciate it if you could review it.

  5. RussellSpitzer commented on Aug 18, 2025

    @RussellSpitzer
    Member

    @manuzhang

    I have created and submitted the PR.

    I would appreciate it if you could review it.

    Thanks for your work here, but I believe we already have an open PR that's just waiting for some renders of the new layout
    #13816 - Let's review and get that one in if we can

  6. JeonDaehong commented on Aug 18, 2025

    @JeonDaehong
    Contributor

    @manuzhang

    I have created and submitted the PR.

    I would appreciate it if you could review it.

    Thanks for your work here, but I believe we already have an open PR that's just waiting for some renders of the new layout
    #13816 - Let's review and get that one in if we can

    I was hoping to contribute as quickly as possible, so it’s a bit disappointing.

    In that case, would it be possible to assign me another issue I could work on?

    I’ll be going on a business trip soon, so I’d like to make some contributions before then.

  7. RussellSpitzer commented on Aug 18, 2025

    @RussellSpitzer
    Member

    We generally do not do issue assignment because more often than not it leads to an issue stagnating. It's best to just check and see whether there are any pull requests tied to the issue you would like to fix before attempting to fix it. If there is a pull-request up it's also a great contribution to the community to review and assist in getting it over the finish line. We strongly discourage opening another PR when there already exists an open piece of work from another community member unless you have confirmed with them that they are no longer working on the issue.

    If you do find another issue please let me or other members know and we can help you with reviews and such

  8. JeonDaehong commented on Aug 18, 2025

    @JeonDaehong
    Contributor

    @RussellSpitzer

    Ah, I see now.

    I thought the process was that I should first leave a comment to express my intention to contribute, and then it would be reserved until I submit a PR.

    But actually, it’s that whoever starts the PR first takes precedence, right? :)

    Thanks for kindly explaining this to me!

  9. RussellSpitzer commented on Aug 19, 2025

    @RussellSpitzer
    Member

    Yes sorry, we essentially have the problem that many people are willing to have an issue assigned them to them, but our followthrough rate is very low. Because of that we generally do not allow assignment. If you are interested, raise a PR, first come first serve :). Now of course if a PR is abandoned we can always move on from an open PR without a contributor but we tend to want to encourage anyone who raises PR's to keep contributing so we bias for users who do that.

  10. JeonDaehong commented on Aug 20, 2025

    @JeonDaehong
    Contributor

    Yes sorry, we essentially have the problem that many people are willing to have an issue assigned them to them, but our followthrough rate is very low. Because of that we generally do not allow assignment. If you are interested, raise a PR, first come first serve :). Now of course if a PR is abandoned we can always move on from an open PR without a contributor but we tend to want to encourage anyone who raises PR's to keep contributing so we bias for users who do that.

    Yes! Thank you for kindly explaining this.
    I’ll make sure to contribute many PRs in the future.

  11. JeonDaehong commented on Aug 24, 2025

    @JeonDaehong
    Contributor

    @RussellSpitzer

    It has been over 10 days without any further updates on the previous PR. Would it be okay if I continue working on this issue and submit a fix?

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

    beginnerIssues for apache iceberg beginners, enjoy to contribute !docsgood first issueGood for newcomersimprovementPR that improves existing functionality

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions