[
https://issues.apache.org/jira/browse/IMPALA-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738510#comment-16738510
]
Tim Armstrong commented on IMPALA-8059:
---------------------------------------
You would assume. There's a minor weirdness that we'd like to fix - IMPALA-7551
- that it's assumed rows are available when Open() returns from the topmost
plan node, rather than when the first batch is produced. The assumption is that
producing each batch is relatively quick, but there are many examples when it's
not (e.g. the sleep())
> 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
