You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Leping Huang (Jira)" <ji...@apache.org> on 2020/08/20 19:48:00 UTC

[jira] [Assigned] (HUDI-323) Docker demo/integ-test stdout/stderr output only available on process exit

     [ https://issues.apache.org/jira/browse/HUDI-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leping Huang reassigned HUDI-323:
---------------------------------

    Assignee: Leping Huang

> Docker demo/integ-test stdout/stderr output only available on process exit
> --------------------------------------------------------------------------
>
>                 Key: HUDI-323
>                 URL: https://issues.apache.org/jira/browse/HUDI-323
>             Project: Apache Hudi
>          Issue Type: Test
>          Components: newbie, Testing
>            Reporter: Vinoth Chandar
>            Assignee: Leping Huang
>            Priority: Major
>              Labels: help-wanted, newbie
>
> 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 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)