[
https://issues.apache.org/jira/browse/IMPALA-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738450#comment-16738450
]
Tim Armstrong commented on IMPALA-8059:
---------------------------------------
[~stakiar] the FINISHED HS2 state doesn't actually mean the query finished
executing, it actually means that the query is ready for the client to fetch
results. The execution model is different from Hive so the names don't map
directly
I wrote up a doc with some more info to share with a couple of people a while
ago so might as well share this publicly (I'll add it to the wiki too):
https://docs.google.com/document/d/1i838cTzPXHp_5zHE9twJHVVzxVnQDMIMVeNBttsFT5E/edit?usp=sharing
> TestWebPage::test_backend_states is flaky
> -----------------------------------------
>
> Key: IMPALA-8059
> URL: https://issues.apache.org/jira/browse/IMPALA-8059
> Project: IMPALA
> Issue Type: Bug
> Reporter: Pooja Nilangekar
> Assignee: Sahil Takiar
> Priority: Blocker
> Labels: broken-build, flaky-test
>
> test_backend_states is flaky. The query reaches the _"FINISHED"_ state before
> it's state is verified by the python test. Here are the relevant log:
> {code:java}
> 07:33:45 ----------------------------- Captured stderr call
> -----------------------------
> 07:33:45 -- executing async: localhost:21000
> 07:33:45 select sleep(10000) from functional.alltypes limit 1;
> 07:33:45
> 07:33:45 -- 2019-01-08 07:31:57,952 INFO MainThread: Started query
> 7f46f15ed4d6d0f6:4d58cdbc00000000
> 07:33:45 -- getting state for operation:
> <tests.common.impala_connection.OperationHandle object at 0x5b3db90>
> {code}
> This bug was introduced by IMPALA-7625.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
