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

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

Commit 779a0943acc3ea47c25a27d1661011c93123ced0 in impala's branch 
refs/heads/master from wzhou-code
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=779a0943a ]

IMPALA-11715: test_resource_limits_kudu fails

test_resource_limits_kudu assumes scan_bytes_limit not enforced for
Kudu. Commit for IMPALA-11702 added bytes read counter for Kudu scanner
so that scan_bytes_limit was enforced for Kudu.

This patch fixs test_resource_limits_kudu.

Testing:
 - Executed test_resource_limits_kudu in a loop on local machine.
 - Passed core run.

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


> test_resource_limits_kudu fails
> -------------------------------
>
>                 Key: IMPALA-11715
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11715
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Wenzhe Zhou
>            Priority: Critical
>             Fix For: Impala 4.3.0
>
>
> h2. Error Details
> {noformat}
> query_test/test_resource_limits.py:54: in test_resource_limits_kudu     
> self.run_test_case('QueryTest/query-resource-limits-kudu', vector) 
> common/impala_test_suite.py:707: in run_test_case     result = exec_fn(query, 
> user=test_section.get('USER', '').strip() or None) 
> common/impala_test_suite.py:645: in __exec_in_impala     result = 
> self.__execute_query(target_impalad_client, query, user=user) 
> common/impala_test_suite.py:981: in __execute_query     return 
> impalad_client.execute(query, user=user) common/impala_connection.py:212: in 
> execute     return self.__beeswax_client.execute(sql_stmt, user=user) 
> beeswax/impala_beeswax.py:189: in execute     handle = 
> self.__execute_query(query_string.strip(), user=user) 
> beeswax/impala_beeswax.py:367: in __execute_query     
> self.wait_for_finished(handle) beeswax/impala_beeswax.py:388: in 
> wait_for_finished     raise ImpalaBeeswaxException("Query aborted:" + 
> error_log, None) E   ImpalaBeeswaxException: ImpalaBeeswaxException: E    
> Query aborted:Query 47412acf5f88fffc:441512c100000000 terminated due to scan 
> bytes limit of 1.00 KB
> {noformat}
> h2. Stack Trace
> {noformat}
> query_test/test_resource_limits.py:54: in test_resource_limits_kudu
>     self.run_test_case('QueryTest/query-resource-limits-kudu', vector)
> common/impala_test_suite.py:707: in run_test_case
>     result = exec_fn(query, user=test_section.get('USER', '').strip() or None)
> common/impala_test_suite.py:645: in __exec_in_impala
>     result = self.__execute_query(target_impalad_client, query, user=user)
> common/impala_test_suite.py:981: in __execute_query
>     return impalad_client.execute(query, user=user)
> common/impala_connection.py:212: in execute
>     return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:189: in execute
>     handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:367: in __execute_query
>     self.wait_for_finished(handle)
> beeswax/impala_beeswax.py:388: in wait_for_finished
>     raise ImpalaBeeswaxException("Query aborted:" + error_log, None)
> E   ImpalaBeeswaxException: ImpalaBeeswaxException:
> E    Query aborted:Query 47412acf5f88fffc:441512c100000000 terminated due to 
> scan bytes limit of 1.00 KB
> {noformat}
> Saw it in https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/6620/
> (please click on "Don't keep this build forever" once resolved)



--
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