Michael Ho created IMPALA-8174:
--
Summary: test_catalog_restart failed with exception "Detected
catalog service ID change"
Key: IMPALA-8174
URL: https://issues.apache.org/jira/browse/IMPALA-8174
Project:
[
https://issues.apache.org/jira/browse/IMPALA-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7504:
---
Target Version: Product Backlog (was: Impala 3.2.0)
> ParseKerberosPrincipal() should use krb5_pars
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reopened IMPALA-8064:
> test_min_max_filters is flaky
> --
>
> Key: IMPALA-8064
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762208#comment-16762208
]
Michael Ho commented on IMPALA-8064:
Looks like the same test is still failing even
Michael Ho created IMPALA-8154:
--
Summary: Disable auth_to_local by default
Key: IMPALA-8154
URL: https://issues.apache.org/jira/browse/IMPALA-8154
Project: IMPALA
Issue Type: Bug
Compo
[
https://issues.apache.org/jira/browse/IMPALA-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758613#comment-16758613
]
Michael Ho commented on IMPALA-6263:
Yet another instance seen recently about it. Ag
[
https://issues.apache.org/jira/browse/IMPALA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757840#comment-16757840
]
Michael Ho commented on IMPALA-8128:
There is a Kudu troubleshooting guide here:
ht
[
https://issues.apache.org/jira/browse/IMPALA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757833#comment-16757833
]
Michael Ho commented on IMPALA-8128:
Just hit a similar case. Seems to be unsynchron
[
https://issues.apache.org/jira/browse/IMPALA-8150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-8150:
---
Description:
{{org.apache.impala.analysis.AuditingTest.TestAccessEventsOnAuthFailure}}
started to f
Michael Ho created IMPALA-8150:
--
Summary: AuditingTest.TestAccessEventsOnAuthFailure
Key: IMPALA-8150
URL: https://issues.apache.org/jira/browse/IMPALA-8150
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6159:
---
Affects Version/s: Impala 2.12.0
> DataStreamSender should transparently handle some connection rese
[
https://issues.apache.org/jira/browse/IMPALA-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6159:
---
Priority: Critical (was: Major)
> DataStreamSender should transparently handle some connection rese
[
https://issues.apache.org/jira/browse/IMPALA-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-8138:
---
Component/s: Distributed Exec
> Re-introduce rpc debugging options
> ---
[
https://issues.apache.org/jira/browse/IMPALA-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755333#comment-16755333
]
Michael Ho commented on IMPALA-8138:
We should consider switching to using DebugActi
Michael Ho created IMPALA-8111:
--
Summary: Document workaround for some authentication issues with
KRPC
Key: IMPALA-8111
URL: https://issues.apache.org/jira/browse/IMPALA-8111
Project: IMPALA
Is
[
https://issues.apache.org/jira/browse/IMPALA-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749308#comment-16749308
]
Michael Ho commented on IMPALA-8027:
The profile didn't suggest much either. The las
[
https://issues.apache.org/jira/browse/IMPALA-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749067#comment-16749067
]
Michael Ho commented on IMPALA-8027:
Looks like the coordinator seems to be slow som
Michael Ho created IMPALA-8006:
--
Summary: Consider replacing the modulus in KrpcDatastreamSender
with fast mod
Key: IMPALA-8006
URL: https://issues.apache.org/jira/browse/IMPALA-8006
Project: IMPALA
Michael Ho created IMPALA-8005:
--
Summary: Randomize partitioning exchanges destinations
Key: IMPALA-8005
URL: https://issues.apache.org/jira/browse/IMPALA-8005
Project: IMPALA
Issue Type: Improv
Michael Ho created IMPALA-7985:
--
Summary: Port RemoteShutdown() to KRPC
Key: IMPALA-7985
URL: https://issues.apache.org/jira/browse/IMPALA-7985
Project: IMPALA
Issue Type: Sub-task
Com
Michael Ho created IMPALA-7984:
--
Summary: Port UpdateFilter() and PublishFilter() to KRPC
Key: IMPALA-7984
URL: https://issues.apache.org/jira/browse/IMPALA-7984
Project: IMPALA
Issue Type: Task
[
https://issues.apache.org/jira/browse/IMPALA-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-4255.
Resolution: Won't Fix
Apparently, some users of Impala still rely on this fancy features to get ev
[
https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720709#comment-16720709
]
Michael Ho edited comment on IMPALA-6692 at 12/13/18 11:55 PM:
---
[
https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720709#comment-16720709
]
Michael Ho commented on IMPALA-6692:
{quote}
Have we seen problems with any operator
[
https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6692:
---
Attachment: profile-spilling.txt
> When partition exchange is followed by sort each sort node become
[
https://issues.apache.org/jira/browse/IMPALA-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-4889.
Resolution: Fixed
Fix Version/s: (was: Not Applicable)
Impala 3.2.0
[
https://issues.apache.org/jira/browse/IMPALA-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7467:
---
Target Version: Product Backlog (was: Impala 3.2.0)
> Port ExecQueryFInstances() to KPRC
>
[
https://issues.apache.org/jira/browse/IMPALA-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-3380:
---
Target Version: Product Backlog, Impala 2.13.0 (was: Impala 2.13.0)
> Add TCP timeouts to all RPCs
[
https://issues.apache.org/jira/browse/IMPALA-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-5119:
---
Target Version: Product Backlog
> Don't make RPCs from Coordinator::UpdateBackendExecStatus()
>
[
https://issues.apache.org/jira/browse/IMPALA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6788:
---
Target Version: Product Backlog
> Query fragments can spend lots of time starting up then fail right
[
https://issues.apache.org/jira/browse/IMPALA-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16716039#comment-16716039
]
Michael Ho commented on IMPALA-7931:
[~tarmstrong], this sounds reasonable to me too
[
https://issues.apache.org/jira/browse/IMPALA-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-6741.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> Profiles of running queries should tell las
[
https://issues.apache.org/jira/browse/IMPALA-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-6754.
Resolution: Fixed
Fix Version/s: Impala 2.12.0
Impala 3.1.0
The problem
[
https://issues.apache.org/jira/browse/IMPALA-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708058#comment-16708058
]
Michael Ho commented on IMPALA-6754:
Things have definitely improved with KRPC. Plea
[
https://issues.apache.org/jira/browse/IMPALA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7232:
---
Labels: supportability (was: )
> Display whether fragment instances' profile is complete
>
[
https://issues.apache.org/jira/browse/IMPALA-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7473:
---
Description:
DecimalValue does not seem to be 16 bytes aligned and impala hits a GPF. I
could only
[
https://issues.apache.org/jira/browse/IMPALA-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7473:
---
Description:
DecimalValue does not seem to be 16 bytes aligned and impala hits a GPF. I
could only
[
https://issues.apache.org/jira/browse/IMPALA-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7473:
---
Summary: RawValue::PrintValue() hits general protection fault with VLOG
level 3 (was: Impala hits g
[
https://issues.apache.org/jira/browse/IMPALA-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701189#comment-16701189
]
Michael Ho edited comment on IMPALA-7903 at 11/28/18 12:02 AM:
---
[
https://issues.apache.org/jira/browse/IMPALA-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701189#comment-16701189
]
Michael Ho commented on IMPALA-7903:
Btw, we have seen similar problem in IMPALA-747
[
https://issues.apache.org/jira/browse/IMPALA-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701132#comment-16701132
]
Michael Ho commented on IMPALA-2990:
The remaining major work item (IMPALA-4555) is
[
https://issues.apache.org/jira/browse/IMPALA-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-2990:
--
Assignee: Thomas Tauber-Marshall (was: Michael Ho)
> Coordinator should timeout a connection
[
https://issues.apache.org/jira/browse/IMPALA-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-2885.
Resolution: Fixed
Fix Version/s: Impala 2.7.0
The other patch I was working on was abandone
[
https://issues.apache.org/jira/browse/IMPALA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-2797:
--
Assignee: (was: Michael Ho)
> scanner threads can act like a thundering herd
> --
[
https://issues.apache.org/jira/browse/IMPALA-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-7829.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> Send the final profile only after all fragm
[
https://issues.apache.org/jira/browse/IMPALA-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-7852.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> test_hash_join_timer flakiness on s3 testin
[
https://issues.apache.org/jira/browse/IMPALA-7879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7879:
---
Issue Type: Improvement (was: Bug)
> Final profiles of queries should be reliably retrievable
> ---
Michael Ho created IMPALA-7879:
--
Summary: Final profiles of queries should be reliably retrievable
Key: IMPALA-7879
URL: https://issues.apache.org/jira/browse/IMPALA-7879
Project: IMPALA
Issue T
[
https://issues.apache.org/jira/browse/IMPALA-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-4475:
---
A patch from [~vukercegovac] is out for review here:
https://gerrit.cloudera.org/#/c/9251/
> Compress
[
https://issues.apache.org/jira/browse/IMPALA-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693818#comment-16693818
]
Michael Ho commented on IMPALA-4475:
Whatever is done here will still have benefit e
[
https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6984:
---
Issue Type: Sub-task (was: Improvement)
Parent: IMPALA-5486
> Coordinator should cancel bac
[
https://issues.apache.org/jira/browse/IMPALA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693795#comment-16693795
]
Michael Ho commented on IMPALA-539:
---
Given that we probably need a timeout for response
[
https://issues.apache.org/jira/browse/IMPALA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692475#comment-16692475
]
Michael Ho commented on IMPALA-539:
---
Ideally, we should always wait for all backend com
[
https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692357#comment-16692357
]
Michael Ho edited comment on IMPALA-6984 at 11/19/18 10:19 PM:
---
[
https://issues.apache.org/jira/browse/IMPALA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692357#comment-16692357
]
Michael Ho commented on IMPALA-6984:
Now that IMPALA-4063 is fixed, we should have a
[
https://issues.apache.org/jira/browse/IMPALA-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690202#comment-16690202
]
Michael Ho commented on IMPALA-7852:
This may be caused by IMPALA-4063. In particula
[
https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687138#comment-16687138
]
Michael Ho commented on IMPALA-7072:
I think we do:
https://www.cloudera.com/docume
[
https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687138#comment-16687138
]
Michael Ho edited comment on IMPALA-7072 at 11/14/18 9:20 PM:
[
https://issues.apache.org/jira/browse/IMPALA-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-4978:
---
Labels: kerberos security (was: security)
> Impala should set the kerberos principal to the FQDN
>
[
https://issues.apache.org/jira/browse/IMPALA-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-4712:
---
Labels: catalog-server kerberos security (was: catalog-server security)
> Transient kerberos authen
[
https://issues.apache.org/jira/browse/IMPALA-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6871:
---
Component/s: Security
> SSL_shutdown: shutdown while in init
>
[
https://issues.apache.org/jira/browse/IMPALA-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-7021:
--
Assignee: (was: Sailesh Mukil)
> Impala query fails with BlockMissingException while HDFS
[
https://issues.apache.org/jira/browse/IMPALA-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-5023:
---
Labels: kerberos (was: )
> supportability: DNS GLSB in front of IMPALA (env: Kerberos+SSL)
> --
[
https://issues.apache.org/jira/browse/IMPALA-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6071:
---
Labels: kerberos supportability (was: supportability)
> impala-shell hang during Kerberos authentic
[
https://issues.apache.org/jira/browse/IMPALA-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-6143:
--
Assignee: (was: Sailesh Mukil)
> Impala returns a series of SSL_connect failures during s
[
https://issues.apache.org/jira/browse/IMPALA-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-4855:
---
Labels: kerberos scalability security (was: scalability security)
> Complex query on large cluster
[
https://issues.apache.org/jira/browse/IMPALA-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-4709:
---
Labels: kerberos (was: )
> [KERBEROS] Improve the error message for impala-shell on Kerberised
> e
[
https://issues.apache.org/jira/browse/IMPALA-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-1770:
---
Labels: kerberos security (was: security)
> Concurrent query right after impala restart can cause c
[
https://issues.apache.org/jira/browse/IMPALA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-3189:
---
Labels: kerberos (was: )
> Address scalability issue with N^2 KDC requests on cluster startup
> ---
[
https://issues.apache.org/jira/browse/IMPALA-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7650:
---
Labels: kerbreos (was: )
> Enable Kerberos by default for mini-cluster test
> -
[
https://issues.apache.org/jira/browse/IMPALA-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7650:
---
Labels: kerberos (was: kerbreos)
> Enable Kerberos by default for mini-cluster test
> -
[
https://issues.apache.org/jira/browse/IMPALA-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7638:
---
Labels: kerberos (was: )
> Lower default timeout for connection setup
> ---
[
https://issues.apache.org/jira/browse/IMPALA-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-4860.
Resolution: Duplicate
Fix Version/s: Not Applicable
> Stagger impala TGS_REQ to KDC
> -
[
https://issues.apache.org/jira/browse/IMPALA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-3189:
---
Labels: kerberos scalability (was: kerberos)
> Address scalability issue with N^2 KDC requests on c
[
https://issues.apache.org/jira/browse/IMPALA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-3189:
--
Assignee: (was: Henry Robinson)
> Address scalability issue with N^2 KDC requests on clus
[
https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7072:
---
Labels: kerberos (was: )
> Support Kerberos auth_to_local rules
> -
[
https://issues.apache.org/jira/browse/IMPALA-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-4860:
---
Labels: kerberos scalability supportability (was: scalability
supportability)
> Stagger impala TGS
[
https://issues.apache.org/jira/browse/IMPALA-6143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-6143:
---
Labels: kerberos (was: )
> Impala returns a series of SSL_connect failures during secure stress tes
[
https://issues.apache.org/jira/browse/IMPALA-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687018#comment-16687018
]
Michael Ho commented on IMPALA-4069:
Now that IMPALA-7213 and IMPALA-4063 are fixed,
[
https://issues.apache.org/jira/browse/IMPALA-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-7072:
--
Assignee: (was: Sailesh Mukil)
> Support Kerberos auth_to_local rules
> -
[
https://issues.apache.org/jira/browse/IMPALA-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-4978:
--
Assignee: (was: Sailesh Mukil)
> Impala should set the kerberos principal to the FQDN
> -
[
https://issues.apache.org/jira/browse/IMPALA-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-4855.
Resolution: Cannot Reproduce
Fix Version/s: Not Applicable
Things have changed quite a lot
[
https://issues.apache.org/jira/browse/IMPALA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-5904:
--
Assignee: (was: Michal Ostrowski)
> Enable ThreadSanitizer for Impala
> -
[
https://issues.apache.org/jira/browse/IMPALA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-4337:
--
Assignee: (was: Michal Ostrowski)
> Wrap long lines in explain plans
> --
[
https://issues.apache.org/jira/browse/IMPALA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-6852:
--
Assignee: (was: Michal Ostrowski)
> Add a section to the query profile covering number of
[
https://issues.apache.org/jira/browse/IMPALA-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-7183:
--
Assignee: (was: Michal Ostrowski)
> We should print the sender name when logging a report
[
https://issues.apache.org/jira/browse/IMPALA-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-6590:
--
Assignee: (was: Michal Ostrowski)
> Disable expr rewrites and codegen for VALUES() statem
[
https://issues.apache.org/jira/browse/IMPALA-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho reassigned IMPALA-2515:
--
Assignee: (was: Michal Ostrowski)
> Impala is unable to read a Parquet decimal column if
[
https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-7148.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
All tests have been re-enabled and the flaky
[
https://issues.apache.org/jira/browse/IMPALA-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-7828.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
Workaround has been merged.
> test_mem_leak(
[
https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678707#comment-16678707
]
Michael Ho commented on IMPALA-7148:
All the tests have been re-enabled now that IMP
[
https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7148:
---
Description:
The underlying bug in IMPALA-6338 was causing a large number of flaky tests and
was tr
[
https://issues.apache.org/jira/browse/IMPALA-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7148:
---
Summary: test_profile_fragment_instances is flaky (was: Re-enable tests
disabled in IMPALA-6338)
>
Michael Ho created IMPALA-7829:
--
Summary: Send the final profile only after all fragment instances
have been closed
Key: IMPALA-7829
URL: https://issues.apache.org/jira/browse/IMPALA-7829
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7828:
---
Description:
Before IMPALA-4063, the error message detected during
{{FragmentInstanceState::Close()
Michael Ho created IMPALA-7828:
--
Summary: test_mem_leak() is flaky
Key: IMPALA-7828
URL: https://issues.apache.org/jira/browse/IMPALA-7828
Project: IMPALA
Issue Type: Bug
Components: B
[
https://issues.apache.org/jira/browse/IMPALA-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-7810.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
Fixed at this commit
[https://github.com/apa
[
https://issues.apache.org/jira/browse/IMPALA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho resolved IMPALA-4063.
Resolution: Fixed
Fix Version/s: Impala 3.2.0
The proposed release of Impala 3.1.0 will not
[
https://issues.apache.org/jira/browse/IMPALA-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ho updated IMPALA-7810:
---
Labels: broken-build (was: )
> query-state.cc:295] Check failed: profile_buf == nullptr
> -
Michael Ho created IMPALA-7810:
--
Summary: query-state.cc:295] Check failed: profile_buf == nullptr
Key: IMPALA-7810
URL: https://issues.apache.org/jira/browse/IMPALA-7810
Project: IMPALA
Issue T
201 - 300 of 542 matches
Mail list logo