[jira] [Created] (IMPALA-8915) Re-fix # links on /catalog page.
Thomas Tauber-Marshall created IMPALA-8915: -- Summary: Re-fix # links on /catalog page. Key: IMPALA-8915 URL: https://issues.apache.org/jira/browse/IMPALA-8915 Project: IMPALA Issue Type: Bug Affects Versions: Impala 3.4.0 Reporter: Thomas Tauber-Marshall Assignee: Tim Armstrong The patch for IMPALA-8879 unintentionally reverted the fix from IMPALA-8901 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IMPALA-8916) Fix auto-refresh/manual refresh interaction on webui
Thomas Tauber-Marshall created IMPALA-8916: -- Summary: Fix auto-refresh/manual refresh interaction on webui Key: IMPALA-8916 URL: https://issues.apache.org/jira/browse/IMPALA-8916 Project: IMPALA Issue Type: Bug Components: Infrastructure Affects Versions: Impala 3.4.0 Reporter: Thomas Tauber-Marshall Assignee: Thomas Tauber-Marshall While clicking around the webui making sure everything works for the Knox integration, I discovered a bug where manually refreshing a page when auto-refresh is turned off leaves the auto-refresh checkbox unchecked but turns auto-refresh back on, as we don't check the value of the checkbox on page load but always just start with auto-refresh on. When this happens, it actually makes it very difficult to turn auto-refresh back off, since if you check and then uncheck the box, it will start and then stop a new refresh interval while leaving the interval that was started on page load running. The workaround would be to check the box, manually refresh the page again, and then uncheck it (or navigate away from the page and then go back) The fix is probably to check the value of the checkbox on page load and disable auto-refresh if its unchecked. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (IMPALA-558) HS2::FetchResults sets hasMoreRows in many cases where no more rows are to be returned
[
https://issues.apache.org/jira/browse/IMPALA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sahil Takiar resolved IMPALA-558.
-
Resolution: Won't Fix
Marking this as "Won't Fix" since it is not a major issue, and fixing this
require a decent amount of code re-factoring. Furthermore, clients that enable
result spooling should see this issue significantly less.
> HS2::FetchResults sets hasMoreRows in many cases where no more rows are to be
> returned
> --
>
> Key: IMPALA-558
> URL: https://issues.apache.org/jira/browse/IMPALA-558
> Project: IMPALA
> Issue Type: Sub-task
> Components: Clients
>Affects Versions: Impala 1.1
>Reporter: Henry Robinson
>Priority: Minor
> Labels: query-lifecycle
>
> The first call to {{FetchResults}} always sets {{hasMoreRows}} even when 0
> rows should be returned. The next call correctly sets {{hasMoreRows ==
> False}}. The upshot is there's always an extra round-trip, although
> correctness isn't affected.
> {code}
> execute_statement_req = TCLIService.TExecuteStatementReq()
> execute_statement_req.sessionHandle = resp.sessionHandle
> execute_statement_req.statement = "SELECT COUNT(*) FROM
> functional.alltypes WHERE 1 = 2"
> execute_statement_resp =
> self.hs2_client.ExecuteStatement(execute_statement_req)
>
> fetch_results_req = TCLIService.TFetchResultsReq()
> fetch_results_req.operationHandle = execute_statement_resp.operationHandle
> fetch_results_req.maxRows = 100
> fetch_results_resp = self.hs2_client.FetchResults(fetch_results_req)
>
> assert not fetch_results_resp.hasMoreRows # Fails
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IMPALA-8917) Including hostnames in debug UI URLs breaks a lot of use cases
Tim Armstrong created IMPALA-8917: - Summary: Including hostnames in debug UI URLs breaks a lot of use cases Key: IMPALA-8917 URL: https://issues.apache.org/jira/browse/IMPALA-8917 Project: IMPALA Issue Type: Bug Components: Infrastructure Affects Versions: Impala 3.4.0 Reporter: Tim Armstrong Assignee: Thomas Tauber-Marshall I've run into multiple cases that got broken by IMPALA-8897. The general problem is the assumption that the hostname that the Impala server refers to itself is resolvable by the client accessing the web UI. Cases I've run into: * In docker and kubernetes, where the internal hostnames aren't visible outside of the internal network * On systems without a DNS-resolvable hostname, e.g. my Ubuntu desktop that I access via a static IP -- This message was sent by Atlassian Jira (v8.3.2#803003)
