prestodb/presto

Allow schema owner to create, drop and rename schema when using FileBasedAccessControl

Open

#20,007 opened on Jun 27, 2023

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Java (5,240 forks)batch import
Securitygood first issuehive-connector

Repository metrics

Stars
 (15,558 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently, when using FileBasedAccessControl in Hive Connector, no one is allowed to create, drop or rename a schema. Ideally, schema owners defined in the config should be allowed to perform these operations.

Contributor guide

Research direction
Investigate FileBasedAccessControl implementation and add authorization checks for schema operations for schema owners.
Tech stack
java
Domain
backendauthorization
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 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
JavaPrestoHive
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50