stackabletech / stackabletech/trino-operator

Fine grained authorisation for CREATE/DROP DDL

Open
#785 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

customer-request
Dominant language
Rust
Stars
63
Forks
13
Avg merge
1d 20h
Merged PRs (30d)
12

Description

As an administrator I would like to be able to separate CREATE TABLE and DROP TABLE privileges. Ideally I would like only the owner/creator of a table to be able to drop that table. At the moment if a user has CREATE privileges on a schema they can drop any table in that schema, which risks accidental data loss if a user can drop another user's table.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue identifies no files, tests, or entry points. Begin by locating where Trino schema CREATE privileges and table DROP authorization are configured or handled, then determine how creator or owner checks should interact with them. Done means CREATE and DROP privileges can be separated and a user's ability to drop another user's table is prevented.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
authorization, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.