Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Support the proposed DictionaryEncoding.custom_metadata (format 1.6) for dictionaries of extension types in IPC

オープン
  • 何か問題がありますか？
#475 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@CurtHagenlocher がすでに取り組んでいます。

2026年10月19日 から。

  • #476 @CurtHagenlocher による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
csharp
領域
backend, databases

調査の方向性

Start by reading ArrowStreamWriter.GetFieldMetadataOffset and MessageSerializer.FieldFromFlatbuffer, then inspect the generated FlatBuffers types and the existing IPC tests. Implement the format 1.6 dictionary value metadata handling in the writer and reader, preserving field metadata for the whole dictionary type. Add the .NET archery dictionary_extension integration case and verify the new behavior against the proposed semantics; the issue notes this work depends on the format vote passing.

索引モデルが issue の本文から書いたものです。

説明

Describe the enhancement requested

In IPC, a dictionary-encoded field has no separate schema node for its value type, so dictionary<values=extension<X>> and extension<X, storage=dictionary<...>> serialize identically, with ARROW:extension:name in Field.custom_metadata. This is tracked upstream as apache/arrow#49704. A format change proposed in apache/arrow#53994 (format version 1.6) adds an optional DictionaryEncoding.custom_metadata that holds the dictionary value type's metadata. That's the IPC counterpart of ArrowSchema.dictionary->metadata in the C Data Interface. Field.custom_metadata keeps describing the whole dictionary type.

The format change is a draft pending a [VOTE] on dev@. Companion PRs: apache/arrow-go#1381, apache/arrow-rs#11622, apache/arrow-nanoarrow#972. This issue is to implement it in Apache.Arrow once the vote passes.

Current Apache.Arrow behavior

  • Writer: ArrowStreamWriter.GetFieldMetadataOffset puts a dictionary value type's extension keys in Field.custom_metadata, which is the same encoding as an extension over a dictionary.
  • Reader: MessageSerializer.FieldFromFlatbuffer resolves Field.custom_metadata against the value type before wrapping it in a DictionaryType, so it reads field-level keys as describing the values. That's the opposite of Arrow C++ and of the proposed spec. As a result:
    • an extension over a dictionary written by Arrow C++ doesn't resolve;
    • Arrow C++ can't read a dictionary<int32, arrow.uuid> written by Apache.Arrow (Invalid storage type for UuidType: dictionary<...>); it can't read the one it writes itself today either.

Proposed work (after the vote)

  1. Regenerate the flatbuffers code for the new DictionaryEncoding.custom_metadata member.
  2. Writer: put a value extension type's ARROW:extension:* keys in DictionaryEncoding.custom_metadata instead of Field.custom_metadata. An extension over a dictionary keeps its keys on the field.
  3. Reader: apply DictionaryEncoding.custom_metadata to the value type before wrapping it in the dictionary type, then apply Field.custom_metadata to the whole dictionary type.
  4. Add the archery dictionary_extension integration case for .NET.

Decision: field-level keys on a dictionary follow the spec, with no fallback

Field.custom_metadata on a dictionary-encoded field describes only the whole dictionary type, as in Arrow C++ and arrow-go, and the reader won't retry it against the value type. Breaking change: dictionary<extension> files written by earlier Apache.Arrow versions (and by every writer before 1.6) will read as a plain dictionary of the storage type, so this needs a release note. #474 makes the same choice for C Data import.

The C Data side is aligned with these semantics in #474.

Component(s)

C#

主要言語
C#
スター
42
フォーク
32
平均マージ
1日 3時間
マージ済み PR（30日）
25

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

apache/arrow-dotnet のほかの issue

apache/arrow-dotnet の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。