Support Iceberg SQL views

Ouverte
  • Quelque chose ne va pas ?
#1,099 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
cpp
Domaine
databases

Piste de recherche

Start with PR #1069 and the existing table catalog APIs, then read the Iceberg view and REST catalog specifications linked in the issue. The scope spans metadata, JSON, lifecycle handling, REST operations, and integration tests; use the listed validation areas to map the work. Done means persisted views support the specified lifecycle through a REST catalog while existing table APIs remain compatible.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Add support for persisted Iceberg SQL views so C++ applications can create, inspect, and manage view definitions through a REST catalog.

The initial metadata types and validation are under review in https://github.com/apache/iceberg-cpp/pull/1069. This issue tracks the complete implementation and expands the view-related work listed in #273.

Proposed scope

  • View metadata types, version history, representations, and validation — #1069.
  • View metadata JSON parsing and serialization, including preservation of unknown representation payloads.
  • View update and requirement types matching the REST wire contract.
  • A metadata builder for schema/version reuse, ordered updates, history retention, and dialect-removal checks.
  • A separate ViewCatalog interface and View handle, with an in-memory implementation for lifecycle tests.
  • REST read operations: load, exists, and paginated list.
  • REST mutations: create, replace, rename, drop, and register, plus property and location updates.

Expected behavior

  • Existing table catalog APIs remain compatible.
  • View handles expose immutable metadata snapshots. Refresh checks the view UUID and installs metadata and response configuration together.
  • SQL representation lookup matches dialects without regard to ASCII case and reports an absent dialect.
  • REST operations honor advertised endpoints and reuse existing authentication and error-handling behavior.
  • Mutations preserve ordered update semantics and report uncertain commit outcomes without automatically replaying the commit.

Validation

  • Metadata and JSON tests using view-format fixtures from the Java and Rust implementations.
  • In-memory lifecycle tests covering history, rollback, schema/version reuse, refresh, and snapshot immutability.
  • REST tests for request/response handling, endpoint discovery, pagination, conflicts, and uncertain commit outcomes.
  • A reference REST catalog integration test covering create, load, replace, rename, and drop.

SQL parsing and planning, materialized views, production storage in non-REST backends, and conditional replacement beyond the standard REST requirements are outside this initial scope.

References:

Langage dominant
C++
Étoiles
227
Forks
142
Merge moyen
3 j 21 min
PR mergées (30 j)
70

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/iceberg-cpp

Toutes les issues de apache/iceberg-cpp

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.