apache/hudi

Docker demo/integ-test stdout/stderr output only available on process exit

Open

#14505 opened on Nov 30, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Java (4,823 stars) (2,431 forks)batch import
area:testsfrom-jiragood first issuepriority:lowpriority:mediumtype:community-support

Description

This is problematic, if the command hangs for e.g, we don't get any logs to indicate where its hanging at.. Better approach is to use something like Piped{Input|Oupput}Stream to implement a thread that can keep printing stdout and stderr as the command runs..

Relevant classes : ITTestHoodieDemo/ ITTTestBase

JIRA info

Contributor guide

Tech stack
javadocker
Domain
testingbackend
Issue type
test
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.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java basicsDocker familiarity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue is that stdout/stderr output from Docker demo/integ test commands is only displayed after the process finishes. This makes debugging hangs difficult. The proposed solution is to use PipedInputStream and PipedOutputStream to implement a thread that continuously reads and prints stdout/stderr as the command runs. The relevant classes are ITTestHoodieDemo and ITTestBase in the test infrastructure. The modifications should be localized to these files.