[jira] [Updated] (IMPALA-7961) Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast

[ https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7961: -- Description: When catalog server is under heavy load with concurrent updates to objects, queries

[jira] [Updated] (IMPALA-7961) Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast

[ https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7961: -- Affects Version/s: Impala 2.12.0 Impala 3.1.0 > Concurrent catalog heavy

[jira] [Commented] (IMPALA-7954) Support automatic invalidates using metastore notification events

[ https://issues.apache.org/jira/browse/IMPALA-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718366#comment-16718366 ] Vihang Karajgaonkar commented on IMPALA-7954: - Adding a google doc where interested folks

[jira] [Assigned] (IMPALA-5832) Simplify the backend's memory ownership and transfer model

[ https://issues.apache.org/jira/browse/IMPALA-5832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-5832: - Assignee: (was: Tim Armstrong) > Simplify the backend's memory ownership and

[jira] [Resolved] (IMPALA-1048) Data sinks do not show up in the exec summary

[ https://issues.apache.org/jira/browse/IMPALA-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-1048. --- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Data sinks do not show up in the

[jira] [Assigned] (IMPALA-6460) More flexible memory-based admission control policies

[ https://issues.apache.org/jira/browse/IMPALA-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6460: - Assignee: (was: Tim Armstrong) > More flexible memory-based admission control

[jira] [Assigned] (IMPALA-4179) Remove RowBatch::MarkNeedsDeepCopy() memory management API

[ https://issues.apache.org/jira/browse/IMPALA-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-4179: - Assignee: (was: Tim Armstrong) > Remove RowBatch::MarkNeedsDeepCopy() memory

[jira] [Resolved] (IMPALA-7906) Crash in JVM PSPromotionManager::copy_to_survivor_space

[ https://issues.apache.org/jira/browse/IMPALA-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7906. --- Resolution: Cannot Reproduce > Crash in JVM PSPromotionManager::copy_to_survivor_space >

[jira] [Created] (IMPALA-7962) Figure out how to handle localtime in docker minicluster containers

Tim Armstrong created IMPALA-7962: - Summary: Figure out how to handle localtime in docker minicluster containers Key: IMPALA-7962 URL: https://issues.apache.org/jira/browse/IMPALA-7962 Project:

[jira] [Updated] (IMPALA-7960) wrong results when comparing timestamp casted to varchar of smaller length to a string literal in a binary predicate

[ https://issues.apache.org/jira/browse/IMPALA-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Garg updated IMPALA-7960: Priority: Blocker (was: Critical) > wrong results when comparing timestamp casted to varchar of

[jira] [Updated] (IMPALA-7961) Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast

[ https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7961: -- Description: When catalog server is under heavy load with concurrent updates to objects, queries

[jira] [Updated] (IMPALA-7961) Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast

[ https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7961: -- Description: When catalog server is under heavy load with concurrent updates to objects, queries

[jira] [Resolved] (IMPALA-7509) Create table after drop can lead to table not found exception

[ https://issues.apache.org/jira/browse/IMPALA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v resolved IMPALA-7509. --- Resolution: Fixed Assignee: Vuk Ercegovac (was: Todd Lipcon) Fix Version/s: Impala

[jira] [Commented] (IMPALA-7802) Implement support for closing idle sessions

[ https://issues.apache.org/jira/browse/IMPALA-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718239#comment-16718239 ] Zoram Thanga commented on IMPALA-7802: -- Thanks for the comment, [~tarmstrong]. You brought up a

[jira] [Updated] (IMPALA-7961) Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast

[ https://issues.apache.org/jira/browse/IMPALA-7961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7961: -- Priority: Critical (was: Major) > Concurrent catalog heavy workloads can cause queries with SYNC_DDL

[jira] [Created] (IMPALA-7961) Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast

bharath v created IMPALA-7961: - Summary: Concurrent catalog heavy workloads can cause queries with SYNC_DDL to fail fast Key: IMPALA-7961 URL: https://issues.apache.org/jira/browse/IMPALA-7961 Project:

[jira] [Commented] (IMPALA-7954) Support automatic invalidates using metastore notification events

[ https://issues.apache.org/jira/browse/IMPALA-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718226#comment-16718226 ] Lars Volker commented on IMPALA-7954: - Thank you for attaching the document, [~vihangk1]. It is

[jira] [Updated] (IMPALA-7960) wrong results when comparing timestamp casted to varchar of smaller length to a string literal in a binary predicate

[ https://issues.apache.org/jira/browse/IMPALA-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Apple updated IMPALA-7960: -- Labels: correctness (was: ) > wrong results when comparing timestamp casted to varchar of smaller

[jira] [Created] (IMPALA-7960) wrong results when comparing timestamp casted to varchar of smaller length to a string literal in a binary predicate

Bikramjeet Vig created IMPALA-7960: -- Summary: wrong results when comparing timestamp casted to varchar of smaller length to a string literal in a binary predicate Key: IMPALA-7960 URL:

[jira] [Work started] (IMPALA-7728) Impala Doc: Add the Changing Privileges section in Impala Sentry doc

[ https://issues.apache.org/jira/browse/IMPALA-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7728 started by Alex Rodoni. --- > Impala Doc: Add the Changing Privileges section in Impala Sentry doc >

[jira] [Updated] (IMPALA-7728) Impala Doc: Add the Changing Privileges section in Impala Sentry doc

[ https://issues.apache.org/jira/browse/IMPALA-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7728: Description: https://gerrit.cloudera.org/#/c/12071/ > Impala Doc: Add the Changing Privileges

[jira] [Resolved] (IMPALA-5821) Distinguish numeric types and show implicit cast in EXTENDED explain plans

[ https://issues.apache.org/jira/browse/IMPALA-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman resolved IMPALA-5821. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Distinguish numeric types and show

[jira] [Resolved] (IMPALA-7744) In PlannerTest print the name of a .test file if it diffs

[ https://issues.apache.org/jira/browse/IMPALA-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman resolved IMPALA-7744. Resolution: Won't Fix > In PlannerTest print the name of a .test file if it diffs >

[jira] [Resolved] (IMPALA-6658) Parquet RLE encoding can waste space with small repeated runs

[ https://issues.apache.org/jira/browse/IMPALA-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman resolved IMPALA-6658. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Parquet RLE encoding can waste

[jira] [Resolved] (IMPALA-7801) Remove toSql() from ParseNode interface

[ https://issues.apache.org/jira/browse/IMPALA-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman resolved IMPALA-7801. Resolution: Won't Fix > Remove toSql() from ParseNode interface >

[jira] [Reopened] (IMPALA-7728) Impala Doc: Add the Changing Privileges section in Impala Sentry doc

[ https://issues.apache.org/jira/browse/IMPALA-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reopened IMPALA-7728: - > Impala Doc: Add the Changing Privileges section in Impala Sentry doc >

[jira] [Closed] (IMPALA-7728) Impala Doc: Add the Changing Privileges section in Impala Sentry doc

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

[jira] [Created] (IMPALA-7959) Trace and visualize concurrent Catalog operations

bharath v created IMPALA-7959: - Summary: Trace and visualize concurrent Catalog operations Key: IMPALA-7959 URL: https://issues.apache.org/jira/browse/IMPALA-7959 Project: IMPALA Issue Type:

[jira] [Closed] (IMPALA-2691) Missing examples of using a UDAF with a different intermediate type

[ https://issues.apache.org/jira/browse/IMPALA-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-2691. --- Resolution: Fixed Fix Version/s: impala 2.3 > Missing examples of using a UDAF with a

[jira] [Created] (IMPALA-7958) Instrument catalog lock objects to dump diagnostics

bharath v created IMPALA-7958: - Summary: Instrument catalog lock objects to dump diagnostics Key: IMPALA-7958 URL: https://issues.apache.org/jira/browse/IMPALA-7958 Project: IMPALA Issue Type:

[jira] [Updated] (IMPALA-7450) catalogd should use thread names to make jstack more readable

[ https://issues.apache.org/jira/browse/IMPALA-7450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7450: -- Labels: supportability (was: ) > catalogd should use thread names to make jstack more readable >

[jira] [Resolved] (IMPALA-7939) Impala shell not displaying results for a CTE query.

[ https://issues.apache.org/jira/browse/IMPALA-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-7939. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Impala shell not displaying results

[jira] [Updated] (IMPALA-4212) Explain plan should show the expression evaluated in all exec node

[ https://issues.apache.org/jira/browse/IMPALA-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4212: -- Description: *Problem Statement* The explain plan does not show the expression evaluated at

[jira] [Updated] (IMPALA-7957) UNION ALL query returns incorrect results

[ https://issues.apache.org/jira/browse/IMPALA-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis E Martinez-Poblete updated IMPALA-7957: Description: Synopsis: = UNION ALL query returns incorrect

[jira] [Created] (IMPALA-7957) UNION ALL query returns incorrect results

Luis E Martinez-Poblete created IMPALA-7957: --- Summary: UNION ALL query returns incorrect results Key: IMPALA-7957 URL: https://issues.apache.org/jira/browse/IMPALA-7957 Project: IMPALA

[jira] [Updated] (IMPALA-7467) Port ExecQueryFInstances() to KPRC

[ 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 >

[jira] [Updated] (IMPALA-3380) Add TCP timeouts to all RPCs that don't block

[ 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

[jira] [Updated] (IMPALA-5119) Don't make RPCs from Coordinator::UpdateBackendExecStatus()

[ 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() >

[jira] [Updated] (IMPALA-6788) Query fragments can spend lots of time starting up then fail right after "starting" all backends

[ 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

[jira] [Commented] (IMPALA-7956) Use Impala SQL parser in Impala shell

[ https://issues.apache.org/jira/browse/IMPALA-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717692#comment-16717692 ] Tim Armstrong commented on IMPALA-7956: --- Two options I mentioned on the CR: * Get rid of the

[jira] [Resolved] (IMPALA-7945) test_hdfs_timeout.py fails on Centos6/python2.6

[ https://issues.apache.org/jira/browse/IMPALA-7945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe McDonnell resolved IMPALA-7945. --- Resolution: Fixed Fix Version/s: Impala 3.2.0 > test_hdfs_timeout.py fails on

[jira] [Created] (IMPALA-7956) Use Impala SQL parser in Impala shell

Fredy Wijaya created IMPALA-7956: Summary: Use Impala SQL parser in Impala shell Key: IMPALA-7956 URL: https://issues.apache.org/jira/browse/IMPALA-7956 Project: IMPALA Issue Type:

[jira] [Updated] (IMPALA-7824) Running INVALIDATE METADATA with authorization enabled can cause a hang if Sentry is unavailable

[ https://issues.apache.org/jira/browse/IMPALA-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya updated IMPALA-7824: - Description: When authorization is enabled and Sentry is unavailable, calling INVALIDATE