[
https://issues.apache.org/jira/browse/IMPALA-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847870#comment-16847870
]
Michael Brown commented on IMPALA-3336:
---
I haven't looked at this in a long time, but if it helps
[
https://issues.apache.org/jira/browse/IMPALA-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835705#comment-16835705
]
Michael Brown commented on IMPALA-2990:
---
Congrats on resolving this!
> Coordinator should timeout
[
https://issues.apache.org/jira/browse/IMPALA-8175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763780#comment-16763780
]
Michael Brown commented on IMPALA-8175:
---
https://gerrit.cloudera.org/c/12412/
> centos6:
Michael Brown created IMPALA-8175:
-
Summary: centos6: tests_minicluster_obj fails with pgrep usage
error
Key: IMPALA-8175
URL: https://issues.apache.org/jira/browse/IMPALA-8175
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-8128.
---
Resolution: Duplicate
> Build failure: Kudu functional data load - Kudu crashed
>
[
https://issues.apache.org/jira/browse/IMPALA-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-8171.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> stress test doesn't work against
[
https://issues.apache.org/jira/browse/IMPALA-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-8169.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> update some random query generator
[
https://issues.apache.org/jira/browse/IMPALA-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762283#comment-16762283
]
Michael Brown commented on IMPALA-8171:
---
There's an easy one line fix to unblock this but I want
[
https://issues.apache.org/jira/browse/IMPALA-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762282#comment-16762282
]
Michael Brown commented on IMPALA-8171:
---
See all the {{bin/start-daemon.sh}} processes. In
Michael Brown created IMPALA-8171:
-
Summary: stress test doesn't work against minicluster
Key: IMPALA-8171
URL: https://issues.apache.org/jira/browse/IMPALA-8171
Project: IMPALA
Issue Type:
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762216#comment-16762216
]
Michael Brown commented on IMPALA-8064:
---
[~poojanilangekar] If you can get access to the profiles,
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-8091.
---
Resolution: Fixed
> minicluster kudu failure: Cannot initialize clock: failed to wait for
Michael Brown created IMPALA-8169:
-
Summary: update some random query generator infra settings
Key: IMPALA-8169
URL: https://issues.apache.org/jira/browse/IMPALA-8169
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-8113.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> test_aggregation and
[
https://issues.apache.org/jira/browse/IMPALA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751703#comment-16751703
]
Michael Brown commented on IMPALA-8115:
---
I noticed this because I posted
[
https://issues.apache.org/jira/browse/IMPALA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8115:
--
Summary: some jenkins workers slow to do real work due to dpkg lock
conflicts (was: some
[
https://issues.apache.org/jira/browse/IMPALA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8115:
--
Description:
A Jenkins worker for label {{ubuntu-16.04}} took about 15 minutes to start
Michael Brown created IMPALA-8115:
-
Summary: some jenkins workers slow to spawn to to dpkg lock
conflicts
Key: IMPALA-8115
URL: https://issues.apache.org/jira/browse/IMPALA-8115
Project: IMPALA
Michael Brown created IMPALA-8113:
-
Summary: test_aggregation and test_avro_primitive_in_list fail in
S3
Key: IMPALA-8113
URL: https://issues.apache.org/jira/browse/IMPALA-8113
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8112:
--
Labels: flaky (was: )
> test_cancel_select with debug action failed with unexpected error
>
[
https://issues.apache.org/jira/browse/IMPALA-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8112:
--
Comment: was deleted
(was: This has happened once on a downstream CI job
[
https://issues.apache.org/jira/browse/IMPALA-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751610#comment-16751610
]
Michael Brown commented on IMPALA-8112:
---
This has happened once on a downstream CI job
Michael Brown created IMPALA-8112:
-
Summary: test_cancel_select with debug action failed with
unexpected error
Key: IMPALA-8112
URL: https://issues.apache.org/jira/browse/IMPALA-8112
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-8091.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
This is all upstream is able to do at
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-8091 started by Michael Brown.
-
> minicluster kudu failure: Cannot initialize clock: failed to wait for
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown reassigned IMPALA-8091:
-
Assignee: Michael Brown (was: Thomas Tauber-Marshall)
> minicluster kudu failure:
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749232#comment-16749232
]
Michael Brown commented on IMPALA-8091:
---
Relevant code in {{testdata/cluster/admin}}:
{noformat}
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749190#comment-16749190
]
Michael Brown commented on IMPALA-8091:
---
On Ubuntu 16, the {{ntp}} package provides {{ntp-wait}}.
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749176#comment-16749176
]
Michael Brown commented on IMPALA-8091:
---
This affected numerous runs over a quiet weekend without
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8091:
--
Priority: Blocker (was: Critical)
> minicluster kudu failure: Cannot initialize clock:
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749157#comment-16749157
]
Michael Brown commented on IMPALA-8091:
---
This is a lot of diagnostic info...
{noformat}
I0116
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8091:
--
Component/s: (was: Backend)
Infrastructure
> minicluster kudu failure:
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8091:
--
Summary: minicluster kudu failure: Cannot initialize clock: failed to wait
for clock sync
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749143#comment-16749143
]
Michael Brown commented on IMPALA-8091:
---
The failure isn't easy to triage from a console log.
[
https://issues.apache.org/jira/browse/IMPALA-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749130#comment-16749130
]
Michael Brown commented on IMPALA-8091:
---
I've seen this too, and I think this is likely an
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746539#comment-16746539
]
Michael Brown commented on IMPALA-8064:
---
That's how I read that, too. My point is I didn't see
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746525#comment-16746525
]
Michael Brown commented on IMPALA-8064:
---
Something curious here as someone who doesn't know all
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746521#comment-16746521
]
Michael Brown commented on IMPALA-8064:
---
Profile for above uploaded as {{profile.txt}}.
>
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8064:
--
Attachment: profile.txt
> test_min_max_filters is flaky
> --
>
>
[
https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746518#comment-16746518
]
Michael Brown commented on IMPALA-8064:
---
[~janulatha] This is still happening on master in a
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740721#comment-16740721
]
Michael Brown edited comment on IMPALA-8069 at 1/11/19 7:47 PM:
I'm also
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8069:
--
Labels: crash query_generator regression (was: crash query_generator)
> crash in
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740721#comment-16740721
]
Michael Brown commented on IMPALA-8069:
---
I'm also going to consider this a regression, because a
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740713#comment-16740713
]
Michael Brown commented on IMPALA-8069:
---
Not sure if [~mostrows] is available to work on this or
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-8069:
--
Labels: crash query_generator (was: query_generator)
> crash in impala::Sorter::Run::Run
>
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740708#comment-16740708
]
Michael Brown commented on IMPALA-8069:
---
Yep, that's it. Analysis doesn't permit me even to run
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740700#comment-16740700
]
Michael Brown commented on IMPALA-8069:
---
Oh, I think I know why this happens now: IMPALA-6323
[
https://issues.apache.org/jira/browse/IMPALA-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740610#comment-16740610
]
Michael Brown commented on IMPALA-8069:
---
If my Git is right this may have been around since
Michael Brown created IMPALA-8069:
-
Summary: crash in impala::Sorter::Run::Run
Key: IMPALA-8069
URL: https://issues.apache.org/jira/browse/IMPALA-8069
Project: IMPALA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/IMPALA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-7736.
---
Resolution: Won't Fix
For me this happens when you run concurrent_select.py from master
Michael Brown created IMPALA-7910:
-
Summary: COMPUTE STATS does an unnecessary REFRESH after writing
to the Metastore
Key: IMPALA-7910
URL: https://issues.apache.org/jira/browse/IMPALA-7910
Project:
[
https://issues.apache.org/jira/browse/IMPALA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown deleted IMPALA-6853:
--
> COMPUTE STATS does an unnecessary REFRESH after writing to the Metastore
>
[
https://issues.apache.org/jira/browse/IMPALA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-6853:
--
Comment: was deleted
(was: Bell Canada seems to be facing this issue,)
> COMPUTE STATS does
[
https://issues.apache.org/jira/browse/IMPALA-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown reassigned IMPALA-7901:
-
Assignee: Alex Rodoni
> Docs problem describing Kudu partitioning syntax
>
[
https://issues.apache.org/jira/browse/IMPALA-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7863:
--
Attachment: (was: 007.jpg)
> To solve Gmail Server Error 007
>
[
https://issues.apache.org/jira/browse/IMPALA-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7863:
--
Description:
The Gmail Problem is quite common among Gmail users. All of the Gmail users
[
https://issues.apache.org/jira/browse/IMPALA-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7804:
--
Target Version: Impala 3.2.0
> Various scanner tests intermittently failing on S3 on
[
https://issues.apache.org/jira/browse/IMPALA-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7804:
--
Affects Version/s: (was: Impala 3.1.0)
Impala 3.2.0
> Various
[
https://issues.apache.org/jira/browse/IMPALA-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7804:
--
Priority: Blocker (was: Critical)
> Various scanner tests intermittently failing on S3 on
[
https://issues.apache.org/jira/browse/IMPALA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7837:
--
Target Version: Impala 3.2.0 (was: Impala 3.1.0)
> SCAN_BYTES_LIMIT="100M" test failing to
[
https://issues.apache.org/jira/browse/IMPALA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7837:
--
Affects Version/s: (was: Impala 3.1.0)
Impala 3.2.0
>
Michael Brown created IMPALA-7837:
-
Summary: SCAN_BYTES_LIMIT="100M" test failing to raise exception
in release build
Key: IMPALA-7837
URL: https://issues.apache.org/jira/browse/IMPALA-7837
Project:
[
https://issues.apache.org/jira/browse/IMPALA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16680092#comment-16680092
]
Michael Brown commented on IMPALA-7837:
---
[~bikramjeet.vig] Gave this to you to look at, please
[
https://issues.apache.org/jira/browse/IMPALA-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-7809.
---
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> test_concurrent_schema_change
[
https://issues.apache.org/jira/browse/IMPALA-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7809 started by Michael Brown.
-
> test_concurrent_schema_change incompatible with Kudu 1.9
>
Michael Brown created IMPALA-7809:
-
Summary: test_concurrent_schema_change incompatible with Kudu 1.9
Key: IMPALA-7809
URL: https://issues.apache.org/jira/browse/IMPALA-7809
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown reassigned IMPALA-7736:
-
Assignee: Michael Brown
> stress: AssertionError: The number of executing queries is
[
https://issues.apache.org/jira/browse/IMPALA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669410#comment-16669410
]
Michael Brown commented on IMPALA-7736:
---
I finally got time to come back to this, and I have a way
[
https://issues.apache.org/jira/browse/IMPALA-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-5103.
---
Resolution: Cannot Reproduce
> gerrit-verify-dryrun can spin off competing Jobs
>
[
https://issues.apache.org/jira/browse/IMPALA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659627#comment-16659627
]
Michael Brown commented on IMPALA-7736:
---
So I did some combing to find where else this may have
[
https://issues.apache.org/jira/browse/IMPALA-7736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7736:
--
Description:
I'd heard about this anecdotally but haven't seen it until now:
{noformat}
Done
Michael Brown created IMPALA-7736:
-
Summary: stress: AssertionError: The number of executing queries
is negative
Key: IMPALA-7736
URL: https://issues.apache.org/jira/browse/IMPALA-7736
Project:
[
https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7727:
--
Attachment: 3.1-compute-stats-profile.txt
3.1-child-profile.txt
[
https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657183#comment-16657183
]
Michael Brown commented on IMPALA-7727:
---
I played around with this a little bit more and the
[
https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7727:
--
Summary: failed compute stats child query status no longer propagates to
parent query (was:
[
https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16655993#comment-16655993
]
Michael Brown commented on IMPALA-7727:
---
We've been hit by bugs like this before, like
Michael Brown created IMPALA-7727:
-
Summary: compute stats child query errors no longer propagate to
parent query
Key: IMPALA-7727
URL: https://issues.apache.org/jira/browse/IMPALA-7727
Project:
[
https://issues.apache.org/jira/browse/IMPALA-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-7693.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
https://gerrit.cloudera.org/#/c/11651/
Michael Brown created IMPALA-7696:
-
Summary: llvm crash in custom cluster test
Key: IMPALA-7696
URL: https://issues.apache.org/jira/browse/IMPALA-7696
Project: IMPALA
Issue Type: Bug
Michael Brown created IMPALA-7693:
-
Summary: stress test binary search fails to set query names
Key: IMPALA-7693
URL: https://issues.apache.org/jira/browse/IMPALA-7693
Project: IMPALA
Issue
[
https://issues.apache.org/jira/browse/IMPALA-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7693 started by Michael Brown.
-
> stress test binary search fails to set query names
>
[
https://issues.apache.org/jira/browse/IMPALA-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642195#comment-16642195
]
Michael Brown commented on IMPALA-7677:
---
This simplified query also produces the crash:
{noformat}
Michael Brown created IMPALA-7677:
-
Summary: multiple count(distinct): Check failed:
!hash_partitions_.empty()
Key: IMPALA-7677
URL: https://issues.apache.org/jira/browse/IMPALA-7677
Project: IMPALA
[
https://issues.apache.org/jira/browse/IMPALA-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634216#comment-16634216
]
Michael Brown commented on IMPALA-6900:
---
IMPALA-7605 was duped to this. IMPALA-7605 is a P1
[
https://issues.apache.org/jira/browse/IMPALA-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-6900:
--
Priority: Blocker (was: Major)
> Invalidate metadata operation is ignored at a coordinator
[
https://issues.apache.org/jira/browse/IMPALA-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626027#comment-16626027
]
Michael Brown commented on IMPALA-7605:
---
[~bharathv] It reproduces for me at hash
[
https://issues.apache.org/jira/browse/IMPALA-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624214#comment-16624214
]
Michael Brown commented on IMPALA-7605:
---
I've been able to, yes. I also had done a ./buildall.sh
[
https://issues.apache.org/jira/browse/IMPALA-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7605:
--
Labels: regression (was: )
> AnalysisException when first accessing Hive-create table on
[
https://issues.apache.org/jira/browse/IMPALA-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624026#comment-16624026
]
Michael Brown commented on IMPALA-7605:
---
bq. Upon the first access, AnalysisException is raised.
[
https://issues.apache.org/jira/browse/IMPALA-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624016#comment-16624016
]
Michael Brown commented on IMPALA-7605:
---
[~bharathv] I've attached 3.0 vs. 3.1 logs, and the
[
https://issues.apache.org/jira/browse/IMPALA-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-7605:
--
Attachment: metadata-bug.sh
3.1-logs.tar.gz
3.0-logs.tar.gz
>
Michael Brown created IMPALA-7605:
-
Summary: AnalysisException when first accessing Hive-create table
on pristine HMS
Key: IMPALA-7605
URL: https://issues.apache.org/jira/browse/IMPALA-7605
Project:
[
https://issues.apache.org/jira/browse/IMPALA-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597825#comment-16597825
]
Michael Brown commented on IMPALA-7487:
---
[~tarmstrong] I'm probably not going to get to this
[
https://issues.apache.org/jira/browse/IMPALA-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595179#comment-16595179
]
Michael Brown commented on IMPALA-7487:
---
Oops, I realized I'm seeing something slightly different,
[
https://issues.apache.org/jira/browse/IMPALA-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown reassigned IMPALA-7487:
-
Assignee: Michael Brown (was: Tim Armstrong)
> Failures in stress test when running
[
https://issues.apache.org/jira/browse/IMPALA-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16595140#comment-16595140
]
Michael Brown commented on IMPALA-7487:
---
I finally saw this last night. Not sure why I hadn't been
[
https://issues.apache.org/jira/browse/IMPALA-7488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592080#comment-16592080
]
Michael Brown commented on IMPALA-7488:
---
Fwiw, I saw this once before the IMPALA-7407 fix and
[
https://issues.apache.org/jira/browse/IMPALA-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592069#comment-16592069
]
Michael Brown commented on IMPALA-7487:
---
[~tarmstrong] Let me know if you need help especially if
[
https://issues.apache.org/jira/browse/IMPALA-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown resolved IMPALA-7460.
---
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> update paramiko and fabric
>
[
https://issues.apache.org/jira/browse/IMPALA-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-7460 started by Michael Brown.
-
> update paramiko and fabric
> --
>
>
1 - 100 of 153 matches
Mail list logo
