trinodb/trino

Prefer using 'not allowed' in error messages instead of 'not supported'

Open

#7,369 opened on Mar 20, 2021

View on GitHub
 (14 comments) (2 reactions) (1 assignee)Java (2,678 forks)batch import
good first issueuser experience

Repository metrics

Stars
 (9,113 stars)
PR merge metrics
 (Avg merge 5d 9h) (306 merged PRs in 30d)

Description

"Not supported" may mean that something is not yet implemented and not yet supported. While using "not allowed" suggest that this is not allowed by the design.

Contributor guide

Research direction
Search the codebase for all error messages containing 'not supported' and evaluate whether they should be changed to 'not allowed' to reflect design constraints rather than missing implementation.
Tech stack
java
Domain
backenddatabase
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90