[ 
https://issues.apache.org/jira/browse/IMPALA-13584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947983#comment-17947983
 ] 

ASF subversion and git services commented on IMPALA-13584:
----------------------------------------------------------

Commit 96ae16b60bc37e8b38ab3d598c7e867ea1e1d427 in impala's branch 
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=96ae16b60 ]

IMPALA-13584: Add option to shows num row report in impala-shell

In beeswax all statements with the exception of USE print
'Fetched X row(s) in Ys', while in HS2 some statements (REFRESH,
INVALIDATE) metadata does not print it. While these statements always
return 0 rows, the amount of time spent with the statement can be
useful.

This patch modifies add impala-shell to let it print elapsed time for
that query, even if query is not expected to return result metadata.
Added --beeswax_compat_num_rows option in impala-shell. It default to
False. If this option is set (True), 'Fetched 0 row(s) in' will be
printed for all Impala protocol, just like beeswax. One exception for
this is USE query, which will remain silent.

Testing:
- Added test_beeswax_compat_num_rows in test_shell_interactive.py.
- Pass test_shell_interactive.py.

Change-Id: Id76ede98c514f73ff1dfa123a0d951e80e7508b4
Reviewed-on: http://gerrit.cloudera.org:8080/22813
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Inconsistent Fetched ... row(s)  output in Beeswax / hs2
> --------------------------------------------------------
>
>                 Key: IMPALA-13584
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13584
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Clients
>            Reporter: Csaba Ringhofer
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 5.0.0
>
>
> In beeswax all statements with the exception of USE print Fetched .. row(s), 
> while in HS2 some statements (REFRESH, INVALIDATE) metadata does not print 
> it. While these statements always return 0 rows, the amount of time spent 
> with the statement can be useful.
> The difference comes from expect_result_metadata():
> https://github.com/apache/impala/blob/756d9af1c9a12d40b5f5e23fecfce373c056c693/shell/impala_client.py#L1121
> https://github.com/apache/impala/blob/756d9af1c9a12d40b5f5e23fecfce373c056c693/shell/impala_client.py#L1542



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to