trinodb/trino

Make default target result size configurable in ExecutingStatementResource

Open

#2,210 opened on Dec 5, 2019

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (9,113 stars) (2,678 forks)batch import
enhancementgood first issue

Description

https://github.com/prestodb/presto/issues/11908 mentions targetresultsize, is anyone open to a pr to make it configurable in server side properties? ie so folks can try 4mb instead of 1mb. returning 1gb data into reporting tool with odbc/jdbc is really slow. dumping to file on presto server is fast but not an option because the reporting tool cant access files on presto server

Contributor guide

Tech stack
java
Domain
backendperformance
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic JavaUnderstanding of Trino's query execution
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requests making the target result size in ExecutingStatementResource configurable. Start by reviewing the referenced issue #11908 to understand the context. Check how other configuration properties are implemented in Trino (e.g., Config classes and their usage). Then modify ExecutingStatementResource to accept a new configuration property, and add the property to the server side properties. Ensure to update any relevant tests and documentation.