[
https://issues.apache.org/jira/browse/IMPALA-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258803#comment-17258803
]
guojingfeng commented on IMPALA-8962:
-------------------------------------
Hi there, to reproduce this case you can execute this SQL with ImpalaJDBC which
depend on tpcds dataset.
{{}}
{code:java}
select i_item_desc from tpcds_parquet.item where i_item_id='AAAAAAAAGPHDAAAA'
union all
select cast(sleep(20000) as string)
union all
select i_item_desc from tpcds_parquet.item where
i_item_id='AAAAAAAACAMCAAAA'{code}
Execute this case on impala beeswax cli will got result like this:
{code:java}
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| i_item_desc |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Brilliant ships see individually also small ministers. Expected, competitive
attitudes may send there gross metres; units used |
| Nuclear, long women improve better years; complex characters should not take
away middle, clear players. Arms delete. Doors may not remember expensive, old
develo |
| Nuclear, long women improve better years; complex characters should not take
away middle, clear players. Arms delete. Doors may not remember expensive, old
develo |
| Whole critics kiss executives. Slow, usual movements circumvent as from a
difficulties. Low, european children make also girls. Individuals work yet
eligible topics. Social unions t |
| Relevant conditions worry by the stages. Attractive products wish also |
| Relevant conditions worry by the stages. Attractive products wish also |
| 1 |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Fetched 7 row(s) in 25.95s{code}
same sql executed by ImpalaJDBC will just got empty resultset after default
FETCH_ROWS_TIMEOUT_MS of 10 seconds.
> FETCH_ROWS_TIMEOUT_MS should apply before rows are available
> ------------------------------------------------------------
>
> Key: IMPALA-8962
> URL: https://issues.apache.org/jira/browse/IMPALA-8962
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Fix For: Impala 3.4.0
>
>
> IMPALA-7312 added a fetch timeout controlled by the query option
> {{FETCH_ROWS_TIMEOUT_MS}}. The issue is that the timeout only applies after
> the *first* batch of rows are available. The issue is that both Beeswax and
> HS2 clients call {{request_state->BlockOnWait}} inside
> {{ImpalaServer::FetchInternal}}. The call to {{BlockOnWait}} blocks until
> rows are ready to be consumed via {{ClientRequestState::FetchRows}}.
> So clients can still end up blocking indefinitely waiting for the first row
> batch to appear.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
