apache/gravitino

[Subtask] Support policies for view metadata objects

Open

#12,500 opened on Aug 18, 2026

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Java (887 forks)auto 404
good first issuesubtask

Repository metrics

Stars
 (3,058 stars)
PR merge metrics
 (Avg merge 6d 6h) (148 merged PRs in 30d)

Description

Describe the subtask

Support associating policies with VIEW metadata objects through the existing metadata object policy REST APIs.

Currently, VIEW exists in MetadataObject.Type, but it is excluded from PolicyManager.SUPPORTED_METADATA_OBJECT_TYPES_FOR_POLICIES. As a result, policy association requests for views are rejected with Cannot associate policies for unsupported metadata object type VIEW.

Implementation scope:

  • Add VIEW to the supported metadata object types in PolicyManager.
  • Clean up view policy relations when a view is dropped.
  • Extend catalog and schema cascade cleanup for view policy relations across H2, MySQL, and PostgreSQL.
  • Update docs/open-api/policies.yaml to include VIEW.
  • Add unit and integration tests covering policy association, listing, retrieval, removal, direct view deletion, and cascade cleanup.

The completed view tag implementation in #11844 and #11897 can be used as a reference.

This task covers the server, core relational storage, OpenAPI, and their tests. Typed Java and Python client APIs can be handled in follow-up issues.

This task extends the current direct object-policy model and does not implement the policy-on-tag model proposed in #12176.

Parent issue

#604

Contributor guide

Research direction
Start by examining the PolicyManager class to see how supported metadata object types are defined. Add VIEW to the SUPPORTED METADATA OBJECT TYPES FOR POLICIES set. Then investigate how view policy relations are cleaned up when a view is dropped, and extend the cascade cleanup for H2, MySQL, and PostgreSQL. Update the OpenAPI specification to include VIEW. Finally, add unit and integration tests covering the policy associations and cascade cleanup.
Tech stack
javamysqlpostgresqlrest apisql
Domain
backendapidatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaSQLREST API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35