[jira] [Resolved] (IMPALA-2063) impala 'cancelled' query status now has extra characters in it

[ https://issues.apache.org/jira/browse/IMPALA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-2063. Resolution: Fixed Fix Version/s: Impala 3.1.0 Fixed at

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/25/18 3:28 AM: --- The devil,

[jira] [Created] (IMPALA-7755) IS [NOT] DISTINCT FROM rewrite rules don't handle aggregates

Paul Rogers created IMPALA-7755: --- Summary: IS [NOT] DISTINCT FROM rewrite rules don't handle aggregates Key: IMPALA-7755 URL: https://issues.apache.org/jira/browse/IMPALA-7755 Project: IMPALA

[jira] [Created] (IMPALA-7754) Expressions sometimes not re-analyzed after rewrite

Paul Rogers created IMPALA-7754: --- Summary: Expressions sometimes not re-analyzed after rewrite Key: IMPALA-7754 URL: https://issues.apache.org/jira/browse/IMPALA-7754 Project: IMPALA Issue

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/25/18 3:19 AM: --- The devil,

[jira] [Created] (IMPALA-7753) Invalid logic when rewriting ORDER BY clause expressions

Paul Rogers created IMPALA-7753: --- Summary: Invalid logic when rewriting ORDER BY clause expressions Key: IMPALA-7753 URL: https://issues.apache.org/jira/browse/IMPALA-7753 Project: IMPALA

[jira] [Created] (IMPALA-7752) Invalid test logic in ExprRewriterTest

Paul Rogers created IMPALA-7752: --- Summary: Invalid test logic in ExprRewriterTest Key: IMPALA-7752 URL: https://issues.apache.org/jira/browse/IMPALA-7752 Project: IMPALA Issue Type: Bug

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/25/18 2:54 AM: --- The devil,

[jira] [Commented] (IMPALA-7371) TestInsertQueries.test_insert fails on S3 with 0 rows returned

[ https://issues.apache.org/jira/browse/IMPALA-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663083#comment-16663083 ] Tim Armstrong commented on IMPALA-7371: --- [~bharathv] it looks like this was a metadata loading

[jira] [Assigned] (IMPALA-7371) TestInsertQueries.test_insert fails on S3 with 0 rows returned

[ https://issues.apache.org/jira/browse/IMPALA-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7371: - Assignee: bharath v (was: Tim Armstrong) > TestInsertQueries.test_insert fails on S3

[jira] [Commented] (IMPALA-7371) TestInsertQueries.test_insert fails on S3 with 0 rows returned

[ https://issues.apache.org/jira/browse/IMPALA-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663081#comment-16663081 ] Tim Armstrong commented on IMPALA-7371: --- It looked like the problematic query was

[jira] [Updated] (IMPALA-7371) TestInsertQueries.test_insert fails on S3 with 0 rows returned

[ https://issues.apache.org/jira/browse/IMPALA-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7371: -- Component/s: (was: Backend) Catalog > TestInsertQueries.test_insert

[jira] [Updated] (IMPALA-7371) TestInsertQueries.test_insert fails on S3 with 0 rows returned

[ https://issues.apache.org/jira/browse/IMPALA-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7371: -- Affects Version/s: (was: Impala 3.1.0) Impala 3.0 >

[jira] [Commented] (IMPALA-7371) TestInsertQueries.test_insert fails on S3 with 0 rows returned

[ https://issues.apache.org/jira/browse/IMPALA-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663074#comment-16663074 ] Tim Armstrong commented on IMPALA-7371: --- Just some more data points. This failed when run without

[jira] [Commented] (IMPALA-6271) Impala daemon should log a message when it's being shut down

[ https://issues.apache.org/jira/browse/IMPALA-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663042#comment-16663042 ] Tim Armstrong commented on IMPALA-6271: --- [~pranay_singh] [~lv] just a heads up that I'm probably

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/25/18 12:25 AM: The

[jira] [Commented] (IMPALA-5200) Profile timers not updated during long-running sort

[ https://issues.apache.org/jira/browse/IMPALA-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663037#comment-16663037 ] Joe McDonnell commented on IMPALA-5200: --- Regardless of whether we have something equivalent to the

[jira] [Commented] (IMPALA-7750) Additional FE optimizations for CASE expressions

[ https://issues.apache.org/jira/browse/IMPALA-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662994#comment-16662994 ] Paul Rogers commented on IMPALA-7750: - Some of the limitations described here may actually be due to

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/24/18 11:29 PM: The

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/24/18 11:07 PM: The

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/24/18 11:03 PM: The

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers edited comment on IMPALA-7655 at 10/24/18 11:00 PM: The

[jira] [Commented] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662835#comment-16662835 ] Paul Rogers commented on IMPALA-7655: - The devil, on this kind of change, is always in the details.

[jira] [Comment Edited] (IMPALA-110) Add support for multiple distinct operators in the same query block

[ https://issues.apache.org/jira/browse/IMPALA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662627#comment-16662627 ] Greg Rahn edited comment on IMPALA-110 at 10/24/18 9:02 PM: [~Tagar] - So the

[jira] [Assigned] (IMPALA-7749) Merge aggregation node memory estimate is incorrectly influenced by limit

[ https://issues.apache.org/jira/browse/IMPALA-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7749: Assignee: Pooja Nilangekar (was: Bikramjeet Vig) > Merge aggregation node

[jira] [Commented] (IMPALA-7727) failed compute stats child query status no longer propagates to parent query

[ https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662808#comment-16662808 ] bharath v commented on IMPALA-7727: --- Correct. > failed compute stats child query status no longer

[jira] [Commented] (IMPALA-7564) Conservative FK/PK join type detection with complex equi-join conjuncts

[ https://issues.apache.org/jira/browse/IMPALA-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662783#comment-16662783 ] Paul Rogers commented on IMPALA-7564: - Expanding on the previous note, suppose we have a star

[jira] [Comment Edited] (IMPALA-110) Add support for multiple distinct operators in the same query block

[ https://issues.apache.org/jira/browse/IMPALA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662704#comment-16662704 ] Ruslan Dautkhanov edited comment on IMPALA-110 at 10/24/18 7:17 PM:

[jira] [Commented] (IMPALA-110) Add support for multiple distinct operators in the same query block

[ https://issues.apache.org/jira/browse/IMPALA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662704#comment-16662704 ] Ruslan Dautkhanov commented on IMPALA-110: -- [~grahn]] Yes, we would like to keep this session

[jira] [Commented] (IMPALA-7714) Statestore::Subscriber::SetLastTopicVersionProcessed() crashed in AtomicInt64::Store()

[ https://issues.apache.org/jira/browse/IMPALA-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662701#comment-16662701 ] Tim Armstrong commented on IMPALA-7714: --- I reverted http://gerrit.cloudera.org:8080/10847 and have

[jira] [Commented] (IMPALA-7727) failed compute stats child query status no longer propagates to parent query

[ https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662696#comment-16662696 ] Tim Armstrong commented on IMPALA-7727: --- Hmm, ok, so there was still a bug before that where the

[jira] [Reopened] (IMPALA-6955) Timeout when starting test_query_expiration custom cluster

[ https://issues.apache.org/jira/browse/IMPALA-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vuk Ercegovac reopened IMPALA-6955: --- Just saw this again. Lets keep it open in case it becomes more frequent. > Timeout when

[jira] [Commented] (IMPALA-7727) failed compute stats child query status no longer propagates to parent query

[ https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662674#comment-16662674 ] bharath v commented on IMPALA-7727: --- TL;DR It's funny how this surfaced now. It was broken for a while

[jira] [Updated] (IMPALA-7750) Additional FE optimizations for CASE expressions

[ https://issues.apache.org/jira/browse/IMPALA-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7750: Description: The current FE {{CASE}} rewrite code in

[jira] [Updated] (IMPALA-7750) Additional FE optimizations for CASE expressions

[ https://issues.apache.org/jira/browse/IMPALA-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7750: Description: The current FE {{CASE}} rewrite code in

[jira] [Commented] (IMPALA-7733) TestInsertParquetQueries.test_insert_parquet is flaky in S3 due to rename

[ https://issues.apache.org/jira/browse/IMPALA-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662632#comment-16662632 ] Vuk Ercegovac commented on IMPALA-7733: --- Here is another one. The direct cause differs, but fwict,

[jira] [Commented] (IMPALA-110) Add support for multiple distinct operators in the same query block

[ https://issues.apache.org/jira/browse/IMPALA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662627#comment-16662627 ] Greg Rahn commented on IMPALA-110: -- [~Tagar] - So the use case here is you'd still like to get the

[jira] [Updated] (IMPALA-4889) Use sidecars for Thrift-wrapped RPC payloads

[ https://issues.apache.org/jira/browse/IMPALA-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4889: --- Target Version: Impala 3.2.0 (was: Product Backlog) > Use sidecars for Thrift-wrapped RPC payloads

[jira] [Updated] (IMPALA-4555) Don't cancel query for failed ReportExecStatus (done=false) RPC

[ https://issues.apache.org/jira/browse/IMPALA-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4555: --- Target Version: Impala 3.2.0 Labels: (was: impala) > Don't cancel query for failed

[jira] [Updated] (IMPALA-2990) Coordinator should timeout a connection for an unresponsive backend

[ https://issues.apache.org/jira/browse/IMPALA-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-2990: --- Target Version: Impala 3.2.0 (was: Product Backlog) > Coordinator should timeout a connection for

[jira] [Updated] (IMPALA-7213) Port ReportExecStatus() RPCs to KRPC

[ https://issues.apache.org/jira/browse/IMPALA-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-7213: --- Target Version: Impala 3.2.0 > Port ReportExecStatus() RPCs to KRPC >

[jira] [Updated] (IMPALA-4063) Make fragment instance reports per-query (or per-host) instead of per-fragment instance.

[ https://issues.apache.org/jira/browse/IMPALA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-4063: --- Target Version: Impala 3.2.0, Impala 2.13.0 (was: Impala 2.13.0) > Make fragment instance reports

[jira] [Resolved] (IMPALA-7677) multiple count(distinct): Check failed: !hash_partitions_.empty()

[ https://issues.apache.org/jira/browse/IMPALA-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Tauber-Marshall resolved IMPALA-7677. Resolution: Fixed Fix Version/s: Impala 3.1.0 > multiple

[jira] [Commented] (IMPALA-7677) multiple count(distinct): Check failed: !hash_partitions_.empty()

[ https://issues.apache.org/jira/browse/IMPALA-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662597#comment-16662597 ] ASF subversion and git services commented on IMPALA-7677: - Commit

[jira] [Commented] (IMPALA-7740) Incorrect doc description for nvl2()

[ https://issues.apache.org/jira/browse/IMPALA-7740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662596#comment-16662596 ] ASF subversion and git services commented on IMPALA-7740: - Commit

[jira] [Commented] (IMPALA-7739) Errata in documentation of decode() method

[ https://issues.apache.org/jira/browse/IMPALA-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662595#comment-16662595 ] ASF subversion and git services commented on IMPALA-7739: - Commit

[jira] [Closed] (IMPALA-6832) Impala 3.1 Doc: Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data type1

[ https://issues.apache.org/jira/browse/IMPALA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-6832. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Impala 3.1 Doc: Add additional units to

[jira] [Updated] (IMPALA-2384) Check memory limits in RowBatch constructor and RowBatch::Reset().

[ https://issues.apache.org/jira/browse/IMPALA-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2384: -- Target Version: Product Backlog (was: Impala 3.1.0) > Check memory limits in RowBatch

[jira] [Updated] (IMPALA-7363) Spurious error generated by sequence file scanner with weird scan range length

[ https://issues.apache.org/jira/browse/IMPALA-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7363: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Spurious error generated by sequence file

[jira] [Updated] (IMPALA-7363) Spurious error generated by sequence file scanner with weird scan range length

[ https://issues.apache.org/jira/browse/IMPALA-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7363: -- Target Version: Product Backlog (was: Impala 3.2.0) > Spurious error generated by sequence

[jira] [Updated] (IMPALA-6874) Add more tests for mixed-format tables, including parquet

[ https://issues.apache.org/jira/browse/IMPALA-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6874: -- Target Version: Impala 3.2.0, Impala 2.13.0 (was: Impala 2.13.0, Impala 3.1.0) > Add more

[jira] [Updated] (IMPALA-7561) Expired queries should end up in a consistent state (EXCEPTION, CANCELLED, or something else)

[ https://issues.apache.org/jira/browse/IMPALA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7561: -- Target Version: Product Backlog (was: Impala 3.1.0) > Expired queries should end up in a

[jira] [Updated] (IMPALA-6843) Responses to prioritizedLoad() requests should be returned directly and not via the statestore

[ https://issues.apache.org/jira/browse/IMPALA-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6843: -- Target Version: Product Backlog (was: Impala 3.1.0) > Responses to prioritizedLoad()

[jira] [Updated] (IMPALA-6875) Reservations for ORC scanner

[ https://issues.apache.org/jira/browse/IMPALA-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6875: -- Target Version: Product Backlog (was: Impala 3.1.0) > Reservations for ORC scanner >

[jira] [Resolved] (IMPALA-7628) test_tls_ecdh failing on CentOS 6/Python 2.6

[ https://issues.apache.org/jira/browse/IMPALA-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7628. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Doesn't seem to be reproducing >

[jira] [Updated] (IMPALA-7053) Reorganise query options into groups

[ https://issues.apache.org/jira/browse/IMPALA-7053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7053: -- Target Version: Product Backlog (was: Impala 3.1.0) > Reorganise query options into groups >

[jira] [Updated] (IMPALA-5607) Add additional units to EXTRACT, DATE_PART, TRUNC for temporal data types

[ https://issues.apache.org/jira/browse/IMPALA-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5607: -- Target Version: Product Backlog (was: Impala 3.1.0) > Add additional units to EXTRACT,

[jira] [Updated] (IMPALA-7356) Stress test for memory-based admission control

[ https://issues.apache.org/jira/browse/IMPALA-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7356: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) Some good improvements landed in 3.1 but

[jira] [Updated] (IMPALA-7353) Fix bogus too-high memory estimates

[ https://issues.apache.org/jira/browse/IMPALA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7353: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Fix bogus too-high memory estimates >

[jira] [Updated] (IMPALA-7350) More accurate memory estimates for admission

[ https://issues.apache.org/jira/browse/IMPALA-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7350: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > More accurate memory estimates for

[jira] [Commented] (IMPALA-7714) Statestore::Subscriber::SetLastTopicVersionProcessed() crashed in AtomicInt64::Store()

[ https://issues.apache.org/jira/browse/IMPALA-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662564#comment-16662564 ] Tim Armstrong commented on IMPALA-7714: --- The main thread is in the signal handler at the time of

[jira] [Resolved] (IMPALA-6846) Impala does not retrieve Sentry roles after restart

[ https://issues.apache.org/jira/browse/IMPALA-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-6846. -- Resolution: Cannot Reproduce I'm not able to reproduce this. > Impala does not retrieve

[jira] [Commented] (IMPALA-7714) Statestore::Subscriber::SetLastTopicVersionProcessed() crashed in AtomicInt64::Store()

[ https://issues.apache.org/jira/browse/IMPALA-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662550#comment-16662550 ] Tim Armstrong commented on IMPALA-7714: --- I could repro after about 5 iterations with this command

[jira] [Updated] (IMPALA-7284) Automatically determine shutdown grace period based on configuration

[ https://issues.apache.org/jira/browse/IMPALA-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7284: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Automatically determine shutdown grace

[jira] [Assigned] (IMPALA-7284) Automatically determine shutdown grace period based on configuration

[ https://issues.apache.org/jira/browse/IMPALA-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7284: - Assignee: Tim Armstrong > Automatically determine shutdown grace period based on

[jira] [Commented] (IMPALA-7714) Statestore::Subscriber::SetLastTopicVersionProcessed() crashed in AtomicInt64::Store()

[ https://issues.apache.org/jira/browse/IMPALA-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662489#comment-16662489 ] Tim Armstrong commented on IMPALA-7714: --- Based on the mtime of 08:49 it looks like one crash

[jira] [Comment Edited] (IMPALA-7707) Impala shell takes a long time to execute insert overwrite select from statement

[ https://issues.apache.org/jira/browse/IMPALA-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661954#comment-16661954 ] Donghui Xu edited comment on IMPALA-7707 at 10/24/18 9:26 AM: -- I found the

[jira] [Commented] (IMPALA-7707) Impala shell takes a long time to execute insert overwrite select from statement

[ https://issues.apache.org/jira/browse/IMPALA-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661954#comment-16661954 ] Donghui Xu commented on IMPALA-7707: I found the following statistics abnormal:

[jira] [Updated] (IMPALA-7751) Kudu insert statement should push down range partition predicates

[ https://issues.apache.org/jira/browse/IMPALA-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-7751: --- Attachment: profile.txt > Kudu insert statement should push down range partition predicates

[jira] [Updated] (IMPALA-7751) Kudu insert statement should push down range partition predicates

[ https://issues.apache.org/jira/browse/IMPALA-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-7751: --- Attachment: metrics3.tsv metrics2.tsv metrics1.tsv > Kudu

[jira] [Commented] (IMPALA-7751) Kudu insert statement should push down range partition predicates

[ https://issues.apache.org/jira/browse/IMPALA-7751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661815#comment-16661815 ] Quanlong Huang commented on IMPALA-7751: [~tarmstr...@cloudera.com], [~twm378], [~mjacobs],

[jira] [Created] (IMPALA-7751) Kudu insert statement should push down range partition predicates

Quanlong Huang created IMPALA-7751: -- Summary: Kudu insert statement should push down range partition predicates Key: IMPALA-7751 URL: https://issues.apache.org/jira/browse/IMPALA-7751 Project: