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

[GLib] Rename run-end encoded array values accessor to physical_values

Open Beginner friendly
#51,479 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
c, ruby

Research direction

Look for the GLib run-end encoded array implementation, likely in c_glib/arrow-glib/. Find the property definition for 'values' and rename it to 'physical_values'. Update the corresponding getter function to garrow_run_end_encoded_array_get_physical_values(), deprecate the old one, and update tests and introspection documentation. Check for any Ruby bindings that might be affected by the property name change.

Written by the indexing model from the issue text.

Description

Component: GLib
Describe the enhancement requested

As requested in the review of #51276, track the GLib naming change separately:

  • Rename the run-end encoded array values property to physical_values (GObject property spelling physical-values).
  • Add garrow_run_end_encoded_array_get_physical_values() and deprecate garrow_run_end_encoded_array_get_values() in its favor, preserving the existing accessor for compatibility.
  • Update introspection documentation and tests for the physical child accessor.

The existing property exposes the physical values of the runs. In Ruby, its generated getter shadows Array#values, which is intended to return logical Ruby values. Explicit physical naming separates these meanings; #51276 keeps its Ruby conversion work separate from this GLib API change.

Component(s)

GLib, Ruby

Prepared with OpenAI Codex.

Dominant language
C++
Stars
17.1k
Forks
4.3k
Avg merge
3d 20h
Merged PRs (30d)
99

Contributor guide

Open the contributing guide

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/arrow

All issues in apache/arrow

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.