trinodb/trino

Derive more precise types for EXTRACT

Open

#5,701 opened on Oct 26, 2020

View on GitHubContributor guide
 (3 comments) (0 reactions) (1 assignee)Java (2,678 forks)batch import
good first issue

Repository metrics

Stars
 (9,113 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently, all results are typed as BIGINT. Given the constrained range for each of the field types, we can derive tighter type bounds.

Contributor guide

Research direction
Examine the existing type derivation for EXTRACT in the Trino codebase, particularly the function registry and type coercion logic. Understand the current BIGINT return type and explore how to leverage field specific type bounds.
Tech stack
java
Domain
backend
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.
Half day
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
SQLJavatype systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60