[jira] [Closed] (IMPALA-6668) Impala 2.12 & 3.0 Docs: Adds "Last row fetched" and "Released admission control resources" events to the query timeline
[ https://issues.apache.org/jira/browse/IMPALA-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6668. --- Resolution: Later Will be address in https://issues.apache.org/jira/browse/IMPALA-6836. > Impala 2.12 & 3.0 Docs: Adds "Last row fetched" and "Released admission > control resources" events to the query timeline > --- > > Key: IMPALA-6668 > URL: https://issues.apache.org/jira/browse/IMPALA-6668 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.0, Impala 2.12.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6483) Impala 3.0 & 2.12 Docs: Describe the query option for query time limit
[ https://issues.apache.org/jira/browse/IMPALA-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6483. --- Resolution: Later > Impala 3.0 & 2.12 Docs: Describe the query option for query time limit > -- > > Key: IMPALA-6483 > URL: https://issues.apache.org/jira/browse/IMPALA-6483 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 3.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > > See https://issues.apache.org/jira/browse/IMPALA-6482 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-6835) big query failure by some table should be clearly marked tablename
yyzzjj created IMPALA-6835: -- Summary: big query failure by some table should be clearly marked tablename Key: IMPALA-6835 URL: https://issues.apache.org/jira/browse/IMPALA-6835 Project: IMPALA Issue Type: Improvement Components: Backend Affects Versions: Impala 2.11.0, Impala 3.0, Impala 2.12.0 Reporter: yyzzjj E.g: [https://github.com/apache/impala/blob/830e3346f186aebc879e4ef2927e08db97143100/be/src/exec/kudu-scanner.cc#L338] big sql usually contains dozens of tables， when query fail kudu tserver or master response error info which not contain table name Inconvenient positioning problem which table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-6805) Show current database in Impala shell prompt
[ https://issues.apache.org/jira/browse/IMPALA-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-6805. -- Resolution: Done Fix Version/s: Impala 2.12.0 Impala 3.0 > Show current database in Impala shell prompt > > > Key: IMPALA-6805 > URL: https://issues.apache.org/jira/browse/IMPALA-6805 > Project: IMPALA > Issue Type: Improvement > Components: Clients >Reporter: Fredy Wijaya >Assignee: Fredy Wijaya >Priority: Minor > Labels: shell > Fix For: Impala 3.0, Impala 2.12.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IMPALA-6831) Impala 2.12 Doc: Remove the note about TLS 1.2 from Impala SSL doc
[ https://issues.apache.org/jira/browse/IMPALA-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6831. --- > Impala 2.12 Doc: Remove the note about TLS 1.2 from Impala SSL doc > -- > > Key: IMPALA-6831 > URL: https://issues.apache.org/jira/browse/IMPALA-6831 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 2.12.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > > This should be removed for 2.12.0: > [https://github.com/apache/impala/blob/40ec6d0080638efaf3260672ab54ea4674896c5e/docs/topics/impala_ssl.xml#L176-L181] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-6831) Impala 2.12 Doc: Remove the note about TLS 1.2 from Impala SSL doc
[ https://issues.apache.org/jira/browse/IMPALA-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni resolved IMPALA-6831. - Resolution: Fixed > Impala 2.12 Doc: Remove the note about TLS 1.2 from Impala SSL doc > -- > > Key: IMPALA-6831 > URL: https://issues.apache.org/jira/browse/IMPALA-6831 > Project: IMPALA > Issue Type: Sub-task > Components: Docs >Affects Versions: Impala 2.12.0 >Reporter: Alex Rodoni >Assignee: Alex Rodoni >Priority: Major > > This should be removed for 2.12.0: > [https://github.com/apache/impala/blob/40ec6d0080638efaf3260672ab54ea4674896c5e/docs/topics/impala_ssl.xml#L176-L181] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-6833) Use include-what-you-use to reduce build times
Sailesh Mukil created IMPALA-6833: - Summary: Use include-what-you-use to reduce build times Key: IMPALA-6833 URL: https://issues.apache.org/jira/browse/IMPALA-6833 Project: IMPALA Issue Type: Task Components: Infrastructure Reporter: Sailesh Mukil Kudu has a systematic way of doing this: https://github.com/apache/kudu/tree/master/build-support/iwyu We can adopt the same efforts to improve our build times and have slightly cleaner code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-6832) Impala 3.0 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data types
Alex Rodoni created IMPALA-6832: --- Summary: Impala 3.0 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data types Key: IMPALA-6832 URL: https://issues.apache.org/jira/browse/IMPALA-6832 Project: IMPALA Issue Type: Sub-task Components: Docs Affects Versions: Impala 3.0 Reporter: Alex Rodoni Assignee: Alex Rodoni -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-6711) Flaky test: TestImpalaShellInteractive.test_multiline_queries_in_history
[
https://issues.apache.org/jira/browse/IMPALA-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-6711.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Flaky test: TestImpalaShellInteractive.test_multiline_queries_in_history
>
>
> Key: IMPALA-6711
> URL: https://issues.apache.org/jira/browse/IMPALA-6711
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 2.12.0
>Reporter: Taras Bobrovytsky
>Assignee: Tim Armstrong
>Priority: Critical
> Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> This happened on a 2.x build:
> {noformat}
> shell/test_shell_interactive.py:230: in test_multiline_queries_in_history
> child_proc.expect(prompt_regex)
> ../infra/python/env/lib/python2.6/site-packages/pexpect/__init__.py:1451: in
> expect
> timeout, searchwindowsize)
> ../infra/python/env/lib/python2.6/site-packages/pexpect/__init__.py:1466: in
> expect_list
> timeout, searchwindowsize)
> ../infra/python/env/lib/python2.6/site-packages/pexpect/__init__.py:1568: in
> expect_loop
> raise TIMEOUT(str(err) + '\n' + str(self))
> E TIMEOUT: Timeout exceeded.
> E
> E version: 3.3
> E command:
> /data/jenkins/workspace/impala-asf-2.x-core/repos/Impala/bin/impala-shell.sh
> E args:
> ['/data/jenkins/workspace/impala-asf-2.x-core/repos/Impala/bin/impala-shell.sh']
> E searcher:
> E buffer (last 100 chars): 't.localdomain:21000] > '
> E before (last 100 chars): 't.localdomain:21000] > '
> E after:
> E match: None
> E match_index: None
> E exitstatus: None
> E flag_eof: False
> E pid: 28172
> E child_fd: 10
> E closed: False
> E timeout: 30
> E delimiter:
> E logfile: None
> E logfile_read: None
> E logfile_send: None
> E maxread: 2000
> E ignorecase: False
> E searchwindowsize: None
> E delaybeforesend: 0.05
> E delayafterclose: 0.1
> E delayafterterminate: 0.1{noformat}
>
> This may be related to IMPALA-6582.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IMPALA-6824) Crash in RuntimeProfile::EventSequence::AddNewerEvents() when events_ is empty
[
https://issues.apache.org/jira/browse/IMPALA-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker resolved IMPALA-6824.
-
Resolution: Fixed
> Crash in RuntimeProfile::EventSequence::AddNewerEvents() when events_ is empty
> --
>
> Key: IMPALA-6824
> URL: https://issues.apache.org/jira/browse/IMPALA-6824
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
>Affects Versions: Impala 3.0, Impala 2.12.0
>Reporter: Lars Volker
>Assignee: Lars Volker
>Priority: Blocker
> Fix For: Impala 3.0, Impala 2.12.0
>
>
> When {{events_}} is empty in runtime-profile-counters.h:347, events_.back()
> is undefined. This can lead to a crash. The fix is to check for
> {{events_.empty()}} before calling {{back()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IMPALA-6831) Impala 2.12 Doc: Remove the note about TLS 1.2 from Impala SSL doc
Alex Rodoni created IMPALA-6831: --- Summary: Impala 2.12 Doc: Remove the note about TLS 1.2 from Impala SSL doc Key: IMPALA-6831 URL: https://issues.apache.org/jira/browse/IMPALA-6831 Project: IMPALA Issue Type: Sub-task Components: Docs Affects Versions: Impala 2.12.0 Reporter: Alex Rodoni Assignee: Alex Rodoni -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-5729) Kudu may crash in minicluster if clock becomes unsynchronized
[
https://issues.apache.org/jira/browse/IMPALA-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-5729.
Resolution: Cannot Reproduce
> Kudu may crash in minicluster if clock becomes unsynchronized
> -
>
> Key: IMPALA-5729
> URL: https://issues.apache.org/jira/browse/IMPALA-5729
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
>Affects Versions: Impala 2.10.0
>Reporter: Henry Robinson
>Priority: Major
> Labels: flaky-test, kudu
>
> See e.g. https://jenkins.impala.io/job/gerrit-verify-dryrun/937/consoleFull.
> {code}
> 00:44:28 ] E HiveServer2Error: AnalysisException: Error opening Kudu table
> 'impala::tpch_kudu.lineitem', Kudu error: can not complete before timeout:
> KuduRpc(method=GetTableSchema, tablet=null, attempt=94,
> DeadlineTracker(timeout=18, elapsed=179403), Traces: [0ms] querying
> master, [0ms] Sub rpc: ConnectToMaster sending RPC to server
> master-127.0.0.1:7051, [0ms] Sub rpc: ConnectToMaster received from server
> master-127.0.0.1:7051 response Network error: [peer master-127.0.0.1:7051]
> connection closed, [1ms] delaying RPC due to Service unavailable: Master
> config (127.0.0.1:7051) has no leader. Exceptions received:
> org.apache.kudu.client.RecoverableException: [peer master-127.0.0.1:7051]
> connection closed, [22ms] querying master, [22ms] Sub rpc: ConnectToMaster
> sending RPC to server master-127.0.0.1:7051, [22ms] Sub rpc: ConnectToMaster
> received from server master-127.0.0.1:7051 response Network error: [peer
> master-127.0.0.1:7051] connection closed, [23ms] delaying RPC due to Service
> unavailable: Master config (127.0.0.1:7051) has no leader. Exceptions
> received: org.apache.kudu.client.RecoverableException: [peer
> master-127.0.0.1:7051] connection closed, [42ms] querying master, [42ms] Sub
> rpc: ConnectToMaster sending RPC to server master-127.0.0.1:7051, [42ms] Sub
> rpc: ConnectToMaster received from server master-127.0.0.1:7051 response
> Network error: [peer master-127.0.0.1:7051] connection closed, [43ms]
> delaying RPC due to Service unavailable: Master config (127.0.0.1:7051) has
> no leader. Exceptions received: org.apache.kudu.client.RecoverableException:
> [peer master-127.0.0.1:7051] connection closed, [62ms] querying master,
> [63ms] Sub rpc: ConnectToMaster sending RPC to server master-127.0.0.1:7051,
> [63ms] Sub rpc: ConnectToMaster received from server master-127.0.0.1:7051
> response Network error: [peer master-127.0.0.1:7051] connection closed,
> [63ms] delaying RPC due to Service unavailable: Master config
> (127.0.0.1:7051) has no leader. Exceptions received:
> org.apache.kudu.client.RecoverableException: [peer master-127.0.0.1:7051]
> connection closed, [82ms] querying master, [82ms] Sub rpc: ConnectToMaster
> sending RPC to server master-127.0.0.1:7051, [82ms] Sub rpc: ConnectToMaster
> received from server master-127.0.0.1:7051 response Network error: [peer
> master-127.0.0.1:7051] connection closed, [83ms] delaying RPC due to Service
> unavailable: Master config (127.0.0.1:7051) has no leader. Exceptions
> received: org.apache.kudu.client.RecoverableException: [peer
> master-127.0.0.1:7051] connection closed, [102ms] querying master, [102ms]
> Sub rpc: ConnectToMaster sending RPC to server master-127.0.0.1:7051, [103ms]
> Sub rpc: ConnectToMaster received from server master-127.0.0.1:7051 response
> Network error: [peer master-127.0.0.1:7051] connection closed, [103ms]
> delaying RPC due to Service unavailable: Master config (127.0.0.1:7051) has
> no leader. Exceptions received: org.apache.kudu.client.RecoverableException:
> [peer master-127.0.0.1:7051] connection closed, [162ms] querying master,
> [162ms] Sub rpc: ConnectToMaster sending RPC to server master-127.0.0.1:7051,
> [162ms] Sub rpc: ConnectToMaster received from server master-127.0.0.1:7051
> response Network error: [peer master-127.0.0.1:7051] connection closed,
> [163ms] delaying RPC due to Service unavailable: Master config
> (127.0.0.1:7051) has no leader. Exceptions received:
> org.apache.kudu.client.RecoverableException: [peer master-127.0.0.1:7051]
> connection closed, [242ms] querying master, [242ms] Sub rpc: ConnectToMaster
> sending RPC to server master-127.0.0.1:7051, [242ms] Sub rpc: ConnectToMaster
> received from server master-127.0.0.1:7051 response Network error: [peer
> master-127.0.0.1:7051] connection closed, [243ms] delaying RPC due to Service
> unavailable: Master config (127.0.0.1:7051) has no leader. Exceptions
> received: org.apache.kudu.client.RecoverableException: [peer
> master-127.0.0.1:7051] connection closed, [362ms] querying master, [362ms]
> Sub rpc: ConnectToMaster sending RPC to server
