Zoram Thanga created IMPALA-6271:
Summary: Impala daemon should log a message when it's being shut
down
Key: IMPALA-6271
URL: https://issues.apache.org/jira/browse/IMPALA-6271
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6114.
--
Resolution: Fixed
Fix Version/s: Impala 2.11.0
> Incorrect type deduction causing
Zoram Thanga created IMPALA-6332:
Summary: Impala webserver should return HTTP error code for
missing query profiles
Key: IMPALA-6332
URL: https://issues.apache.org/jira/browse/IMPALA-6332
Project:
Zoram Thanga created IMPALA-6225:
Summary: IMPALA-5599 broke a client software due to precision
change in date-time string
Key: IMPALA-6225
URL: https://issues.apache.org/jira/browse/IMPALA-6225
Zoram Thanga created IMPALA-6307:
Summary: A CTAS query fails with error: AnalysisException:
Duplicate column name:
Key: IMPALA-6307
URL: https://issues.apache.org/jira/browse/IMPALA-6307
Project:
Zoram Thanga created IMPALA-6996:
Summary: PartitionedAggregationNode::Close() should not allocate
memory
Key: IMPALA-6996
URL: https://issues.apache.org/jira/browse/IMPALA-6996
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6225.
--
Resolution: Fixed
Fix Version/s: Impala 2.11.0
> IMPALA-5599 broke a client software
Zoram Thanga created IMPALA-6381:
Summary: test_exchange_delays.py failed on isilon build due to
sender timeout
Key: IMPALA-6381
URL: https://issues.apache.org/jira/browse/IMPALA-6381
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6307.
--
Resolution: Fixed
Fix Version/s: Impala 2.12.0
> A CTAS query fails with error:
Zoram Thanga created IMPALA-7444:
Summary: Improve debug logging of session opening and expiry
Key: IMPALA-7444
URL: https://issues.apache.org/jira/browse/IMPALA-7444
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7444.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Improve debug logging of session
[
https://issues.apache.org/jira/browse/IMPALA-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7014.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Disable stacktrace symbolisation by
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6086.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Use of permanent function should
[
https://issues.apache.org/jira/browse/IMPALA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6764.
--
Resolution: Fixed
Fix Version/s: Impala 2.12.0
> Codegend
Zoram Thanga created IMPALA-7285:
Summary: Restructure analyzer code to perform security/access
checks before re-analysis
Key: IMPALA-7285
URL: https://issues.apache.org/jira/browse/IMPALA-7285
Zoram Thanga created IMPALA-6895:
Summary: Eliminate SimpleLogger flush threads by inlining flush
Key: IMPALA-6895
URL: https://issues.apache.org/jira/browse/IMPALA-6895
Project: IMPALA
Zoram Thanga created IMPALA-6930:
Summary: Empty --llvm_cpu_attr_whitelist startup argument triggers
crash in LLVM
Key: IMPALA-6930
URL: https://issues.apache.org/jira/browse/IMPALA-6930
Project:
Zoram Thanga created IMPALA-6764:
Summary: Codegend UnionNode::MaterializeBatch() causes memory
corruption crash of Impalad
Key: IMPALA-6764
URL: https://issues.apache.org/jira/browse/IMPALA-6764
[
https://issues.apache.org/jira/browse/IMPALA-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6498.
--
Resolution: Fixed
Fix Version/s: Impala 2.12.0
Impala 3.0
>
Zoram Thanga created IMPALA-6936:
Summary: LLVM in aggressive optimization mode generates toxic x86
assembly for StringFunctions::Trim
Key: IMPALA-6936
URL: https://issues.apache.org/jira/browse/IMPALA-6936
Zoram Thanga created IMPALA-7674:
Summary: Impala should compress older log files
Key: IMPALA-7674
URL: https://issues.apache.org/jira/browse/IMPALA-7674
Project: IMPALA
Issue Type:
Zoram Thanga created IMPALA-8012:
Summary: Log a message when --fe_service_threads have been
allocated
Key: IMPALA-8012
URL: https://issues.apache.org/jira/browse/IMPALA-8012
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7508.
--
Resolution: Fixed
Resolving now.
> Add Impala GDB commands to find fragment instances and
[
https://issues.apache.org/jira/browse/IMPALA-7800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7800.
--
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Reject or timeout new incoming
[
https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-6996:
-
Summary: PartitionedAggregationNode::Close() should not dump stack trace
(was:
Zoram Thanga created IMPALA-6996:
Summary: PartitionedAggregationNode::Close() should not allocate
memory
Key: IMPALA-6996
URL: https://issues.apache.org/jira/browse/IMPALA-6996
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470966#comment-16470966
]
Zoram Thanga commented on IMPALA-6764:
--
[~dhecht]:
>> Do we have an example of the bad IR to x86
[
https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471506#comment-16471506
]
Zoram Thanga commented on IMPALA-6996:
--
Dup'ing this to IMPALA-6997, as the narrowed scope of this
[
https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6996.
--
Resolution: Duplicate
> PartitionedAggregationNode::Close() should not dump stack trace
>
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16513154#comment-16513154
]
Zoram Thanga commented on IMPALA-6086:
--
Here's a rough diff for what I think should be done:
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16513138#comment-16513138
]
Zoram Thanga commented on IMPALA-6086:
--
Thanks for the inputs, [~tarmstrong], [~fredyw]. Agree
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514221#comment-16514221
]
Zoram Thanga commented on IMPALA-6086:
--
In case it was not clear, here's a sample session. User
[
https://issues.apache.org/jira/browse/IMPALA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-4065:
Assignee: Tianyi Wang (was: Zoram Thanga)
> Inline comparator calls into
[
https://issues.apache.org/jira/browse/IMPALA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505508#comment-16505508
]
Zoram Thanga commented on IMPALA-4065:
--
Assigned you the jira, [~tianyiwang].
> Inline comparator
[
https://issues.apache.org/jira/browse/IMPALA-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-6664 started by Zoram Thanga.
> Tag log statements with query-ids
> -
>
>
[
https://issues.apache.org/jira/browse/IMPALA-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-6664:
Assignee: Zoram Thanga
> Tag log statements with query-ids
>
[
https://issues.apache.org/jira/browse/IMPALA-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-6665:
Assignee: Zoram Thanga
> Tag CatalogOp logs with query IDs
>
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-6086:
-
Affects Version/s: Impala 3.1.0
> Use of permanent function should require SELECT privilege on
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495564#comment-16495564
]
Zoram Thanga commented on IMPALA-6086:
--
I just checked on a 2.7 cluster, and it seems like the
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494379#comment-16494379
]
Zoram Thanga commented on IMPALA-6086:
--
Finally had some cycles to dig into this. Looks like
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494461#comment-16494461
]
Zoram Thanga commented on IMPALA-6086:
--
The issue seems to be that the function call "trim('abcd')"
Zoram Thanga created IMPALA-6971:
Summary: Log flooding with unhelpful parsing error message
Key: IMPALA-6971
URL: https://issues.apache.org/jira/browse/IMPALA-6971
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555934#comment-16555934
]
Zoram Thanga commented on IMPALA-6671:
--
This issue has existed since Impala 2.10 (or may be even
[
https://issues.apache.org/jira/browse/IMPALA-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-6671:
-
Affects Version/s: Impala 2.10.0
Impala 2.11.0
> Metadata operations
[
https://issues.apache.org/jira/browse/IMPALA-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7444 started by Zoram Thanga.
> Improve debug logging of session opening and expiry
>
Zoram Thanga created IMPALA-7444:
Summary: Improve debug logging of session opening and expiry
Key: IMPALA-7444
URL: https://issues.apache.org/jira/browse/IMPALA-7444
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-7444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7444.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Improve debug logging of session
[
https://issues.apache.org/jira/browse/IMPALA-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-7014.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Disable stacktrace symbolisation by
[
https://issues.apache.org/jira/browse/IMPALA-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6086.
--
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Use of permanent function should
[
https://issues.apache.org/jira/browse/IMPALA-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554524#comment-16554524
]
Zoram Thanga commented on IMPALA-5058:
--
[~tge...@cloudera.com], this is fixed in CDH 5.15.0.
>
[
https://issues.apache.org/jira/browse/IMPALA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-7508:
-
Labels: debugging supportability (was: supportability)
> Add Impala GDB commands to find
[
https://issues.apache.org/jira/browse/IMPALA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-7508:
-
Labels: supportability (was: )
> Add Impala GDB commands to find fragment instances and
[
https://issues.apache.org/jira/browse/IMPALA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7508 started by Zoram Thanga.
> Add Impala GDB commands to find fragment instances and queries in a core
Zoram Thanga created IMPALA-7508:
Summary: Add Impala GDB commands to find fragment instances and
queries in a core file
Key: IMPALA-7508
URL: https://issues.apache.org/jira/browse/IMPALA-7508
[
https://issues.apache.org/jira/browse/IMPALA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604907#comment-16604907
]
Zoram Thanga commented on IMPALA-6764:
--
IMPALA-6059 changed the implementation of
[
https://issues.apache.org/jira/browse/IMPALA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-6764:
-
Fix Version/s: Impala 2.11.0
> Codegend UnionNode::MaterializeBatch() causes memory corruption
[
https://issues.apache.org/jira/browse/IMPALA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga resolved IMPALA-6764.
--
Resolution: Fixed
Fix Version/s: Impala 2.12.0
> Codegend
[
https://issues.apache.org/jira/browse/IMPALA-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-7014:
Assignee: Zoram Thanga (was: Joe McDonnell)
> Disable stacktrace symbolisation by
[
https://issues.apache.org/jira/browse/IMPALA-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7014 started by Zoram Thanga.
> Disable stacktrace symbolisation by default
>
[
https://issues.apache.org/jira/browse/IMPALA-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542024#comment-16542024
]
Zoram Thanga commented on IMPALA-7288:
--
Possibly introduced by IMPALA-6177?
> Codegen crash in
Zoram Thanga created IMPALA-7285:
Summary: Restructure analyzer code to perform security/access
checks before re-analysis
Key: IMPALA-7285
URL: https://issues.apache.org/jira/browse/IMPALA-7285
[
https://issues.apache.org/jira/browse/IMPALA-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542004#comment-16542004
]
Zoram Thanga commented on IMPALA-7288:
--
FYI, the crash repro's with the latest upstream code as
[
https://issues.apache.org/jira/browse/IMPALA-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-7288:
-
Affects Version/s: Impala 3.1.0
> Codegen crash in FinalizeModule()
>
[
https://issues.apache.org/jira/browse/IMPALA-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537325#comment-16537325
]
Zoram Thanga commented on IMPALA-7178:
--
I wonder if IMPALA-6996 is an instance of this log
[
https://issues.apache.org/jira/browse/IMPALA-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537325#comment-16537325
]
Zoram Thanga edited comment on IMPALA-7178 at 7/9/18 5:47 PM:
--
I wonder if
[
https://issues.apache.org/jira/browse/IMPALA-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531685#comment-16531685
]
Zoram Thanga commented on IMPALA-7194:
--
Lowering priority to Critical, since this issue has been
[
https://issues.apache.org/jira/browse/IMPALA-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-7194:
-
Priority: Critical (was: Blocker)
> Impala crashed at FragmentInstanceState::Open()
>
[
https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-7802:
-
Labels: supportability (was: )
> Implement support for closing idle sessions
>
[
https://issues.apache.org/jira/browse/IMPALA-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga updated IMPALA-7674:
-
Labels: supportability (was: )
> Impala should compress older log files
>
Zoram Thanga created IMPALA-7674:
Summary: Impala should compress older log files
Key: IMPALA-7674
URL: https://issues.apache.org/jira/browse/IMPALA-7674
Project: IMPALA
Issue Type:
[
https://issues.apache.org/jira/browse/IMPALA-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-6664:
Assignee: Philip Zeyliger (was: Zoram Thanga)
> Tag log statements with query-ids
>
Zoram Thanga created IMPALA-8012:
Summary: Log a message when --fe_service_threads have been
allocated
Key: IMPALA-8012
URL: https://issues.apache.org/jira/browse/IMPALA-8012
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718239#comment-16718239
]
Zoram Thanga commented on IMPALA-7802:
--
Thanks for the comment, [~tarmstrong]. You brought up a
[
https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-7802:
Assignee: Zoram Thanga
> Implement support for closing idle sessions
>
[
https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16710704#comment-16710704
]
Zoram Thanga commented on IMPALA-7802:
--
The documentation states that:
{quote}
Once a session is
[
https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7802 started by Zoram Thanga.
> Implement support for closing idle sessions
>
[
https://issues.apache.org/jira/browse/IMPALA-7800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-7800:
Assignee: Zoram Thanga
> Reject or timeout new incoming connections once
[
https://issues.apache.org/jira/browse/IMPALA-7800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739889#comment-16739889
]
Zoram Thanga commented on IMPALA-7800:
--
The current implementation of TAccepQueueServer inherits
[
https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739902#comment-16739902
]
Zoram Thanga commented on IMPALA-7802:
--
Apologies, [~tarmstrong] for not responding sooner. I
[
https://issues.apache.org/jira/browse/IMPALA-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-6665:
Assignee: (was: Zoram Thanga)
> Tag CatalogOp logs with query IDs
>
[
https://issues.apache.org/jira/browse/IMPALA-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-5922:
Assignee: (was: Zoram Thanga)
> Scanners should include file and offset information
[
https://issues.apache.org/jira/browse/IMPALA-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-889:
---
Assignee: (was: Zoram Thanga)
> Add trim() function matching ANSI SQL definition
>
[
https://issues.apache.org/jira/browse/IMPALA-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-8306:
Assignee: (was: Zoram Thanga)
> Debug WebUI's Sessions page verbiage clarification
>
[
https://issues.apache.org/jira/browse/IMPALA-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoram Thanga reassigned IMPALA-7674:
Assignee: (was: Zoram Thanga)
> Impala should compress older log files
>
[
https://issues.apache.org/jira/browse/IMPALA-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792971#comment-16792971
]
Zoram Thanga commented on IMPALA-8310:
--
Sounds good to me.
That said, I wonder how the thread pool
[
https://issues.apache.org/jira/browse/IMPALA-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794014#comment-16794014
]
Zoram Thanga commented on IMPALA-8310:
--
Ahh yes. Thanks [~joemcdonnell].
> Terminate impalad when
86 matches
Mail list logo
