Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Rename position delete index to clarify referenced data file key

Open Beginner friendly
#3,359 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
databases

Research direction

Start in crates/iceberg/src/delete_file_index.rs and read the PopulatedDeleteFileIndex field, its local bindings, references, and comments. Rename pos_deletes_by_path to pos_deletes_by_referenced_data_file consistently, preserving behavior; run the existing delete-file index tests, formatting, and Clippy to verify the change.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem or challenge?

PopulatedDeleteFileIndex::pos_deletes_by_path is keyed by the referenced data file's path. The current name leaves it unclear whether the key is the delete file's own path or the data file it applies to.

This tracks the naming follow-up requested in the #3035 review. In the September 21 review of #3145, mbutrovich explicitly asked for a separate tracking issue. The validation work in #3145 can remain separate.

Describe the solution you'd like

Rename the private field and matching local bindings from pos_deletes_by_path to pos_deletes_by_referenced_data_file in crates/iceberg/src/delete_file_index.rs, updating references and comments consistently. Preserve delete-file applicability, indexing, and scan behavior.

Validation should include the existing delete-file index tests, formatting, and Clippy. This is an internal naming cleanup with no intended public API or behavior change.

Willingness to contribute

I would be willing to contribute to this feature with guidance from the Iceberg Rust community.

Prepared with AI assistance; this issue records the requested follow-up and does not claim an implementation.

Dominant language
Rust
Stars
1.4k
Forks
592
Avg merge
5d 12h
Merged PRs (30d)
59

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/iceberg-rust

All issues in apache/iceberg-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.