[
https://issues.apache.org/jira/browse/IMPALA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586520#comment-16586520
]
Dan Hecht commented on IMPALA-7464:
---
{quote}it calls {{ReleaseExecResource()}} again a
[
https://issues.apache.org/jira/browse/IMPALA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586540#comment-16586540
]
Dan Hecht commented on IMPALA-7464:
---
[~tarmstr...@cloudera.com], do you remember speci
[
https://issues.apache.org/jira/browse/IMPALA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586547#comment-16586547
]
Dan Hecht commented on IMPALA-7464:
---
Yea, that sounds right. But here's what remains u
[
https://issues.apache.org/jira/browse/IMPALA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588172#comment-16588172
]
Dan Hecht commented on IMPALA-7464:
---
Reproducing this requires making this change:
{co
Dan Hecht created IMPALA-7495:
-
Summary: Replace fault_injection_rpc_delay_ms with
DebugAction()
Key: IMPALA-7495
URL: https://issues.apache.org/jira/browse/IMPALA-7495
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611278#comment-16611278
]
Dan Hecht commented on IMPALA-1262:
---
Agree, I would expect exception.
I'm not sure I
[
https://issues.apache.org/jira/browse/IMPALA-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611283#comment-16611283
]
Dan Hecht commented on IMPALA-1262:
---
Just saw IMPALA-7561, which I think answers my qu
[
https://issues.apache.org/jira/browse/IMPALA-7464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7464.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> DCHECK(!released_exec_resources_) is triggere
[
https://issues.apache.org/jira/browse/IMPALA-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-6954:
--
Component/s: Frontend
> Kudu CTAS Loses Partitioning
>
>
>
[
https://issues.apache.org/jira/browse/IMPALA-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460022#comment-16460022
]
Dan Hecht commented on IMPALA-6882:
---
{{asm volatile}} should do the trick, as would usi
[
https://issues.apache.org/jira/browse/IMPALA-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460044#comment-16460044
]
Dan Hecht commented on IMPALA-6882:
---
Oh, weird. I guess technically it's still keeping
[
https://issues.apache.org/jira/browse/IMPALA-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-1034:
-
Assignee: Tim Armstrong (was: Dan Hecht)
Summary: Verify RSS stays within mem_limit + JVM h
[
https://issues.apache.org/jira/browse/IMPALA-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-1871:
-
Assignee: Zoltan Ivanfi (was: Dan Hecht)
[~zi], I've lost track of where this is at. Can you de
[
https://issues.apache.org/jira/browse/IMPALA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-708:
Assignee: (was: Dan Hecht)
This is less relevant with clustering where the hashing no longer ha
[
https://issues.apache.org/jira/browse/IMPALA-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-6970:
-
Assignee: Tim Armstrong
> DiskMgr::AllocateBuffersForRange crashes on failed DCHECK
> --
Dan Hecht created IMPALA-6983:
-
Summary: stress test binary search exits if process mem_limit is
too low
Key: IMPALA-6983
URL: https://issues.apache.org/jira/browse/IMPALA-6983
Project: IMPALA
I
[
https://issues.apache.org/jira/browse/IMPALA-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-6983:
--
Description:
This was running stress test on tpch SF=20 and minicluster process
mem_limit=7857355161.
[
https://issues.apache.org/jira/browse/IMPALA-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-1262:
-
Assignee: Bikramjeet Vig
> user initiated query cancellation should return operation_state =
>
Dan Hecht created IMPALA-6984:
-
Summary: Coordinator should cancel backends when returning EOS
Key: IMPALA-6984
URL: https://issues.apache.org/jira/browse/IMPALA-6984
Project: IMPALA
Issue Type:
Dan Hecht created IMPALA-6993:
-
Summary: Don't print status stack trace when propagating thrift
status in Coordinator::BackendState::Exec()
Key: IMPALA-6993
URL: https://issues.apache.org/jira/browse/IMPALA-6993
[
https://issues.apache.org/jira/browse/IMPALA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468259#comment-16468259
]
Dan Hecht commented on IMPALA-6996:
---
Maybe we should make SetMemLimitExceeded() check i
[
https://issues.apache.org/jira/browse/IMPALA-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468270#comment-16468270
]
Dan Hecht commented on IMPALA-6997:
---
Yeah, I think #2 is the way to go, also noted in I
[
https://issues.apache.org/jira/browse/IMPALA-6993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-6993.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Don't print s
Dan Hecht created IMPALA-7011:
-
Summary: Cleanups around PlanRootSink::CloseConsumer()
Key: IMPALA-7011
URL: https://issues.apache.org/jira/browse/IMPALA-7011
Project: IMPALA
Issue Type: Improvem
[
https://issues.apache.org/jira/browse/IMPALA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470854#comment-16470854
]
Dan Hecht commented on IMPALA-6764:
---
Do we have an example of the bad IR to x86 generat
[
https://issues.apache.org/jira/browse/IMPALA-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471256#comment-16471256
]
Dan Hecht commented on IMPALA-7007:
---
Probably overflowing this:
{code:java}
// Error me
[
https://issues.apache.org/jira/browse/IMPALA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7015:
--
Component/s: Backend
> Insert into Kudu table returns with Status OK even if there are Kudu errors
> --
[
https://issues.apache.org/jira/browse/IMPALA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472341#comment-16472341
]
Dan Hecht commented on IMPALA-7015:
---
FWIW, the code goes out if it's way to "downgrade"
[
https://issues.apache.org/jira/browse/IMPALA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472354#comment-16472354
]
Dan Hecht commented on IMPALA-7015:
---
It was done on purpose for IMPALA-3710.
> Insert
[
https://issues.apache.org/jira/browse/IMPALA-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472386#comment-16472386
]
Dan Hecht commented on IMPALA-7013:
---
cc [~kwho]
> test_insert_permutation failed with
[
https://issues.apache.org/jira/browse/IMPALA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472388#comment-16472388
]
Dan Hecht commented on IMPALA-7015:
---
I wasn't trying to express an opinion, just surfac
[
https://issues.apache.org/jira/browse/IMPALA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472426#comment-16472426
]
Dan Hecht commented on IMPALA-7015:
---
But to clarify, we do report the error in the erro
Dan Hecht created IMPALA-7024:
-
Summary: Convert Coordinator::wait_lock_ from boost::mutex to
SpinLock
Key: IMPALA-7024
URL: https://issues.apache.org/jira/browse/IMPALA-7024
Project: IMPALA
Iss
[
https://issues.apache.org/jira/browse/IMPALA-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-1790.
---
Resolution: Duplicate
> FetchResults() sometimes returns very few resuts
> --
[
https://issues.apache.org/jira/browse/IMPALA-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474634#comment-16474634
]
Dan Hecht commented on IMPALA-4268:
---
[~tarmstrong], do you also expect to solve IMPALA-
[
https://issues.apache.org/jira/browse/IMPALA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-5384.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Simplify coor
[
https://issues.apache.org/jira/browse/IMPALA-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476263#comment-16476263
]
Dan Hecht commented on IMPALA-7023:
---
Do we know the earliest githash we hit this on? Ar
[
https://issues.apache.org/jira/browse/IMPALA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476268#comment-16476268
]
Dan Hecht commented on IMPALA-7033:
---
What git hash did we first observe the failure?
>
[
https://issues.apache.org/jira/browse/IMPALA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476325#comment-16476325
]
Dan Hecht commented on IMPALA-7033:
---
Probably IMPALA-5384, though weird this didn't sho
[
https://issues.apache.org/jira/browse/IMPALA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476336#comment-16476336
]
Dan Hecht commented on IMPALA-7033:
---
I put a review for the revert here: [https://gerri
[
https://issues.apache.org/jira/browse/IMPALA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476636#comment-16476636
]
Dan Hecht commented on IMPALA-7033:
---
The revert has merged. I'm not 100% sure that comm
[
https://issues.apache.org/jira/browse/IMPALA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reopened IMPALA-5384:
---
I backed out the last change because it's suspected that it causes IMPALA-7033.
I think thre is a proble
[
https://issues.apache.org/jira/browse/IMPALA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-7033:
-
Assignee: Dan Hecht
Fix Version/s: Impala 3.1.0
Was able to confirm the race was in the
[
https://issues.apache.org/jira/browse/IMPALA-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7033.
---
Resolution: Fixed
The crash is fixed by the backout.
> Impala crashes on exhaustive release tests
>
[
https://issues.apache.org/jira/browse/IMPALA-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7030.
---
Resolution: Duplicate
Assignee: Dan Hecht
I'm pretty sure this corruption has the same root cau
Dan Hecht created IMPALA-7046:
-
Summary: Add targeted regression test for race in IMPALA-7033
Key: IMPALA-7046
URL: https://issues.apache.org/jira/browse/IMPALA-7046
Project: IMPALA
Issue Type: T
[
https://issues.apache.org/jira/browse/IMPALA-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-6235:
--
Labels: admission-control resource-management (was: resource-management)
> Reduce runtime of test_admi
[
https://issues.apache.org/jira/browse/IMPALA-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7046:
--
Description:
I'd like to add a regression test to trigger the race in IMPALA-7033 more
reliably, but i
[
https://issues.apache.org/jira/browse/IMPALA-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7024.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Convert Coord
[
https://issues.apache.org/jira/browse/IMPALA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-5384.
---
Resolution: Fixed
> Simplify coordinator locking protocol
> -
>
>
[
https://issues.apache.org/jira/browse/IMPALA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487719#comment-16487719
]
Dan Hecht commented on IMPALA-5212:
---
It'd be good to do this to reduce the number of co
[
https://issues.apache.org/jira/browse/IMPALA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488228#comment-16488228
]
Dan Hecht commented on IMPALA-5212:
---
That reminds me that I vaguely recall the S3A path
[
https://issues.apache.org/jira/browse/IMPALA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489278#comment-16489278
]
Dan Hecht commented on IMPALA-7067:
---
Does the close RPC show up in the log? i.e. do we
[
https://issues.apache.org/jira/browse/IMPALA-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489466#comment-16489466
]
Dan Hecht commented on IMPALA-7069:
---
Any idea the earliest githash we first saw this at
[
https://issues.apache.org/jira/browse/IMPALA-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-7068:
-
Assignee: Dan Hecht
> Failed test:
> metadata.test_partition_metadata.TestPartitionMetadataUnco
Dan Hecht created IMPALA-7071:
-
Summary: Make get_fs_path() idempotent
Key: IMPALA-7071
URL: https://issues.apache.org/jira/browse/IMPALA-7071
Project: IMPALA
Issue Type: Improvement
Co
[
https://issues.apache.org/jira/browse/IMPALA-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7068.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Failed test:
> metadata.test_partition_metada
[
https://issues.apache.org/jira/browse/IMPALA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495901#comment-16495901
]
Dan Hecht commented on IMPALA-7097:
---
Please see IMPALA-6050 for some related discussio
[
https://issues.apache.org/jira/browse/IMPALA-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495938#comment-16495938
]
Dan Hecht commented on IMPALA-7098:
---
Why does a scan range correspond to a block group
[
https://issues.apache.org/jira/browse/IMPALA-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495940#comment-16495940
]
Dan Hecht commented on IMPALA-7097:
---
Up to you whether you consider them dups of one a
[
https://issues.apache.org/jira/browse/IMPALA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497246#comment-16497246
]
Dan Hecht commented on IMPALA-7099:
---
[~tarmstrong], I think there was code in there to
[
https://issues.apache.org/jira/browse/IMPALA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498244#comment-16498244
]
Dan Hecht commented on IMPALA-7099:
---
The problem is that the filesystem_client method
Dan Hecht created IMPALA-7109:
-
Summary:
estPartitionMetadata::test_multiple_partitions_same_location uses incorrect
paths
Key: IMPALA-7109
URL: https://issues.apache.org/jira/browse/IMPALA-7109
Project:
[
https://issues.apache.org/jira/browse/IMPALA-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7109:
--
Summary: TestPartitionMetadata::test_multiple_partitions_same_location uses
incorrect paths (was:
es
[
https://issues.apache.org/jira/browse/IMPALA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7099:
--
Priority: Major (was: Blocker)
Lowering priority – the xfail should avoid the build failure. I'll get
[
https://issues.apache.org/jira/browse/IMPALA-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498560#comment-16498560
]
Dan Hecht commented on IMPALA-7098:
---
What value does mBlockSize on the return of hdfsG
[
https://issues.apache.org/jira/browse/IMPALA-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498560#comment-16498560
]
Dan Hecht edited comment on IMPALA-7098 at 6/1/18 8:59 PM:
---
Wh
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500556#comment-16500556
]
Dan Hecht commented on IMPALA-7101:
---
I reproduced a hang by looping test_cancellation.
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500556#comment-16500556
]
Dan Hecht edited comment on IMPALA-7101 at 6/4/18 5:24 PM:
---
I
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500607#comment-16500607
]
Dan Hecht commented on IMPALA-7101:
---
Below are the relevant logs. I think what's happe
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-7101:
-
Assignee: Dan Hecht (was: Tim Armstrong)
> Builds are timing out/hanging
> ---
Dan Hecht created IMPALA-7125:
-
Summary: test_cancellation execute_cancel_test() should have a
delay before fetch
Key: IMPALA-7125
URL: https://issues.apache.org/jira/browse/IMPALA-7125
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-4631.
---
Resolution: Fixed
Yeah, I don't think there's value in keeping this open.
> plan-fragment-executor.
[
https://issues.apache.org/jira/browse/IMPALA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-4063:
-
Assignee: Sailesh Mukil (was: Joe McDonnell)
> Make fragment instance reports per-query (or pe
[
https://issues.apache.org/jira/browse/IMPALA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503547#comment-16503547
]
Dan Hecht commented on IMPALA-341:
--
Things have changed a bit since the original descrip
[
https://issues.apache.org/jira/browse/IMPALA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503551#comment-16503551
]
Dan Hecht commented on IMPALA-341:
--
Once this is fixed let's consider which of the commi
[
https://issues.apache.org/jira/browse/IMPALA-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-6338:
--
Summary: Tests fail due to runtime profile for query with limit missing
pieces (was: Runtime profile
[
https://issues.apache.org/jira/browse/IMPALA-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7133:
--
Description:
An instance of this bug is that we see a "Default TException" error instead of
"Query Id
[
https://issues.apache.org/jira/browse/IMPALA-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7011.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
2.x commit:
commit 3b8a96485e36336c8e823479559c
[
https://issues.apache.org/jira/browse/IMPALA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7101.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Builds are t
[
https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505542#comment-16505542
]
Dan Hecht edited comment on IMPALA- at 6/8/18 12:28 AM:
[
https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505542#comment-16505542
]
Dan Hecht commented on IMPALA-:
---
I don't think we want to guarantee that the profi
[
https://issues.apache.org/jira/browse/IMPALA-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7071.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Make get_fs_
Dan Hecht created IMPALA-7153:
-
Summary: filesystem_client methods expect unusual paths
Key: IMPALA-7153
URL: https://issues.apache.org/jira/browse/IMPALA-7153
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7099.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
I filed IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7153:
--
Labels: ramp-up (was: )
> filesystem_client methods expect unusual paths
> --
[
https://issues.apache.org/jira/browse/IMPALA-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7109.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> TestPartitio
[
https://issues.apache.org/jira/browse/IMPALA-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-6942:
-
Assignee: Dan Hecht
Thanks for the reminder. i can take care of it.
> "Cancelled due to unreac
[
https://issues.apache.org/jira/browse/IMPALA-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512871#comment-16512871
]
Dan Hecht commented on IMPALA-7162:
---
To add to the clarification, regarding idle_sessi
[
https://issues.apache.org/jira/browse/IMPALA-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-6942 started by Dan Hecht.
-
> "Cancelled due to unreachable impalad(s)" error message is misleading
> ---
[
https://issues.apache.org/jira/browse/IMPALA-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7046 started by Dan Hecht.
-
> Add targeted regression test for race in IMPALA-7033
>
[
https://issues.apache.org/jira/browse/IMPALA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-6788 started by Dan Hecht.
-
> Query fragments can spend lots of time starting up then fail right after
> "starti
[
https://issues.apache.org/jira/browse/IMPALA-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-6942.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
commit 76f8ff4a1507c3a7f86eb58dbac191024b59890e
[
https://issues.apache.org/jira/browse/IMPALA-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-7125.
---
Resolution: Not A Problem
Actually, I think we get this coverage already from failure/test_failpoint
[
https://issues.apache.org/jira/browse/IMPALA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514558#comment-16514558
]
Dan Hecht commented on IMPALA-6153:
---
We've been trying to clarify query lifecycle even
[
https://issues.apache.org/jira/browse/IMPALA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514558#comment-16514558
]
Dan Hecht edited comment on IMPALA-6153 at 6/16/18 12:14 AM:
-
[
https://issues.apache.org/jira/browse/IMPALA-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516460#comment-16516460
]
Dan Hecht commented on IMPALA-7183:
---
Is there an easy way to determine which host was
[
https://issues.apache.org/jira/browse/IMPALA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reassigned IMPALA-5202:
-
Assignee: Dan Hecht
> Debug action WAIT in PREPARE leads to hung query that cannot be cancelled
[
https://issues.apache.org/jira/browse/IMPALA-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7181:
--
Labels: broken-build (was: )
> Fix flaky test
> shell/test_shell_commandline.py::TestImpalaShell::te
[
https://issues.apache.org/jira/browse/IMPALA-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht updated IMPALA-7181:
--
Issue Type: Bug (was: Test)
> Fix flaky test
> shell/test_shell_commandline.py::TestImpalaShell::tes
1 - 100 of 128 matches
Mail list logo
