[ https://issues.apache.org/jira/browse/IMPALA-11337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550634#comment-17550634 ]
Joe McDonnell commented on IMPALA-11337: ---------------------------------------- It looks like we lost a flush statement as part of this change: [https://github.com/apache/impala/commit/bc9d7e063dd71f9af75967f8c6af9ac1a6f49149#diff-5496720cbdf14ea8f0a3acf577391bbefe96346b5053ca7fa32590b63c522c15L97] > impala-shell can output the "Fetched X row(s)" line before the actual results > ----------------------------------------------------------------------------- > > Key: IMPALA-11337 > URL: https://issues.apache.org/jira/browse/IMPALA-11337 > Project: IMPALA > Issue Type: Bug > Components: Clients > Affects Versions: Impala 4.2.0 > Reporter: Joe McDonnell > Priority: Major > > In some scenarios, we are seeing that the "Fetched X row(s)" message is > output before the actual data: > {noformat} > Query: SELECT * FROM test_table ORDER BY id DESC > Query submitted at: 2022-06-02 23:53:48 (Coordinator: > https://coordinator:25000) > Query progress can be monitored at: > https://coordinator:25000/query_plan?query_id=9d47858d6659cb87:2ccbdcdf00000000 > Fetched 1 row(s) in 1.59s > 0 john 10{noformat} > The "Fetched X row(s)" message is going to stderr and the results are going > to stdout, so this is not covered completely by the current tests. > Nonetheless, we should expect the "Fetched X row(s)" output to happen after > the results data is written. > We should add tests for this case and make sure that stdout is flushed prior > to writing the "Fetched X row(s)" output. -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org