apache/hudi

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

Open

#14,505 创建于 2025年11月30日

在 GitHub 查看
 (0 评论) (0 反应) (1 负责人)Java (4,823 star) (2,431 fork)batch import
area:testsfrom-jiragood first issuepriority:lowpriority:mediumtype:community-support

描述

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

贡献者指南

技术栈
javadocker
领域
testingbackend
议题类型
test
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Java basicsDocker familiarity
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
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.