[jira] [Resolved] (IMPALA-8658) Populate required Ranger audit fields to be consistent with Hive

[ https://issues.apache.org/jira/browse/IMPALA-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-8658. -- Resolution: Fixed > Populate required Ranger audit fields to be consistent with Hive >

[jira] [Resolved] (IMPALA-8658) Populate required Ranger audit fields to be consistent with Hive

[ https://issues.apache.org/jira/browse/IMPALA-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-8658. -- Resolution: Fixed > Populate required Ranger audit fields to be consistent with Hive >

[jira] [Commented] (IMPALA-7615) Partition metadata mismatch should be handled gracefully in local catalog mode.

[ https://issues.apache.org/jira/browse/IMPALA-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867118#comment-16867118 ] Todd Lipcon commented on IMPALA-7615: - How can this happen? It seems like the request to load the

[jira] [Resolved] (IMPALA-8455) GET_TABLE failed with InvalidStorageDescriptorException

[ https://issues.apache.org/jira/browse/IMPALA-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved IMPALA-8455. - Resolution: Fixed Assignee: bharath v Fix Version/s: Impala 3.3.0 > GET_TABLE

[jira] [Commented] (IMPALA-8544) Expose additional S3A / S3Guard metrics

[ https://issues.apache.org/jira/browse/IMPALA-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867113#comment-16867113 ] Steve Loughran commented on IMPALA-8544: BTW, ,S3 throttling is a per-shard in bucket, and all

[jira] [Commented] (IMPALA-8544) Expose additional S3A / S3Guard metrics

[ https://issues.apache.org/jira/browse/IMPALA-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867110#comment-16867110 ] Steve Loughran commented on IMPALA-8544: With on-demand DDB (HADOOP-15563) DDB throttling is no

[jira] [Commented] (IMPALA-8678) ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest

[ https://issues.apache.org/jira/browse/IMPALA-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867074#comment-16867074 ] Andrew Sherman commented on IMPALA-8678: [~hahao] please can you take a look please as you

[jira] [Assigned] (IMPALA-8678) ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest

[ https://issues.apache.org/jira/browse/IMPALA-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman reassigned IMPALA-8678: -- Assignee: Hao Hao > ToSqlTest falures on S3 (from >

[jira] [Created] (IMPALA-8678) ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest

Andrew Sherman created IMPALA-8678: -- Summary: ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest Key: IMPALA-8678 URL: https://issues.apache.org/jira/browse/IMPALA-8678

[jira] [Created] (IMPALA-8678) ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest

Andrew Sherman created IMPALA-8678: -- Summary: ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest Key: IMPALA-8678 URL: https://issues.apache.org/jira/browse/IMPALA-8678

[jira] [Created] (IMPALA-8677) Removing an unused node does not leave consistent remote scheduling unchanged

Joe McDonnell created IMPALA-8677: - Summary: Removing an unused node does not leave consistent remote scheduling unchanged Key: IMPALA-8677 URL: https://issues.apache.org/jira/browse/IMPALA-8677

[jira] [Commented] (IMPALA-8676) run-all-tests-timeout-check.sh times out after 20 hours

[ https://issues.apache.org/jira/browse/IMPALA-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867037#comment-16867037 ] Andrew Sherman commented on IMPALA-8676: [~dknupp] please reassign as appropriate - could even

[jira] [Assigned] (IMPALA-8676) run-all-tests-timeout-check.sh times out after 20 hours

[ https://issues.apache.org/jira/browse/IMPALA-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman reassigned IMPALA-8676: -- Assignee: Andrew Sherman > run-all-tests-timeout-check.sh times out after 20 hours

[jira] [Created] (IMPALA-8676) run-all-tests-timeout-check.sh times out after 20 hours

Andrew Sherman created IMPALA-8676: -- Summary: run-all-tests-timeout-check.sh times out after 20 hours Key: IMPALA-8676 URL: https://issues.apache.org/jira/browse/IMPALA-8676 Project: IMPALA

[jira] [Assigned] (IMPALA-8676) run-all-tests-timeout-check.sh times out after 20 hours

[ https://issues.apache.org/jira/browse/IMPALA-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman reassigned IMPALA-8676: -- Assignee: David Knupp (was: Andrew Sherman) > run-all-tests-timeout-check.sh times

[jira] [Created] (IMPALA-8676) run-all-tests-timeout-check.sh times out after 20 hours

Andrew Sherman created IMPALA-8676: -- Summary: run-all-tests-timeout-check.sh times out after 20 hours Key: IMPALA-8676 URL: https://issues.apache.org/jira/browse/IMPALA-8676 Project: IMPALA

[jira] [Created] (IMPALA-8675) Remove db/table count metrics from impalad in LocalCatalog mode

Todd Lipcon created IMPALA-8675: --- Summary: Remove db/table count metrics from impalad in LocalCatalog mode Key: IMPALA-8675 URL: https://issues.apache.org/jira/browse/IMPALA-8675 Project: IMPALA

[jira] [Created] (IMPALA-8675) Remove db/table count metrics from impalad in LocalCatalog mode

Todd Lipcon created IMPALA-8675: --- Summary: Remove db/table count metrics from impalad in LocalCatalog mode Key: IMPALA-8675 URL: https://issues.apache.org/jira/browse/IMPALA-8675 Project: IMPALA

[jira] [Assigned] (IMPALA-8665) Include extra info in error message when date cast fails

[ https://issues.apache.org/jira/browse/IMPALA-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiawei Wang reassigned IMPALA-8665: --- Assignee: Jiawei Wang > Include extra info in error message when date cast fails >

[jira] [Assigned] (IMPALA-8634) Catalog client should be resilient to temporary Catalog outage

[ https://issues.apache.org/jira/browse/IMPALA-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar reassigned IMPALA-8634: Assignee: Sahil Takiar > Catalog client should be resilient to temporary Catalog outage

[jira] [Updated] (IMPALA-8656) Support for eagerly fetching and spooling all query result rows

[ https://issues.apache.org/jira/browse/IMPALA-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-8656: - Priority: Critical (was: Major) > Support for eagerly fetching and spooling all query result

[jira] [Assigned] (IMPALA-8673) Add query option to force plan hints for insert queries

[ https://issues.apache.org/jira/browse/IMPALA-8673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Rawat reassigned IMPALA-8673: -- Assignee: Abhishek Rawat > Add query option to force plan hints for insert queries >

[jira] [Updated] (IMPALA-8674) REMOTE runtime filters are always shown as disabled in the final filter routing table

[ https://issues.apache.org/jira/browse/IMPALA-8674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8674: -- Affects Version/s: Impala 3.2.0 > REMOTE runtime filters are always shown as disabled in the

[jira] [Created] (IMPALA-8674) REMOTE runtime filters are always shown as disabled in the final filter routing table

Tim Armstrong created IMPALA-8674: - Summary: REMOTE runtime filters are always shown as disabled in the final filter routing table Key: IMPALA-8674 URL: https://issues.apache.org/jira/browse/IMPALA-8674

[jira] [Created] (IMPALA-8674) REMOTE runtime filters are always shown as disabled in the final filter routing table

Tim Armstrong created IMPALA-8674: - Summary: REMOTE runtime filters are always shown as disabled in the final filter routing table Key: IMPALA-8674 URL: https://issues.apache.org/jira/browse/IMPALA-8674

[jira] [Updated] (IMPALA-8339) Coordinator should be more resilient to fragment instances startup failure

[ https://issues.apache.org/jira/browse/IMPALA-8339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Garg updated IMPALA-8339: Priority: Critical (was: Major) > Coordinator should be more resilient to fragment instances

[jira] [Resolved] (IMPALA-8626) JDBC tests don't seem to be using HTTP

[ https://issues.apache.org/jira/browse/IMPALA-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Tauber-Marshall resolved IMPALA-8626. Resolution: Not A Problem > JDBC tests don't seem to be using HTTP >

[jira] [Resolved] (IMPALA-8626) JDBC tests don't seem to be using HTTP

[ https://issues.apache.org/jira/browse/IMPALA-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Tauber-Marshall resolved IMPALA-8626. Resolution: Not A Problem > JDBC tests don't seem to be using HTTP >

[jira] [Work stopped] (IMPALA-8631) Ensure that cached data is always up to date to avoid reads based on stale metadata for transactional read only tables

[ https://issues.apache.org/jira/browse/IMPALA-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8631 stopped by Todd Lipcon. --- > Ensure that cached data is always up to date to avoid reads based on stale >

[jira] [Work started] (IMPALA-8667) Remove --pull_incremental_statistics flag (on by default)

[ https://issues.apache.org/jira/browse/IMPALA-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8667 started by Todd Lipcon. --- > Remove --pull_incremental_statistics flag (on by default) >

[jira] [Assigned] (IMPALA-8423) Add rule to remove useless SELECT node

[ https://issues.apache.org/jira/browse/IMPALA-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Mate reassigned IMPALA-8423: -- Assignee: Tamas Mate > Add rule to remove useless SELECT node >

[jira] [Work started] (IMPALA-8567) Many random catalog consistency issues with catalog v2/event processor

[ https://issues.apache.org/jira/browse/IMPALA-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8567 started by Todd Lipcon. --- > Many random catalog consistency issues with catalog v2/event processor >

[jira] [Work started] (IMPALA-7534) Handle invalidation races in CatalogdMetaProvider cache

[ https://issues.apache.org/jira/browse/IMPALA-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7534 started by Todd Lipcon. --- > Handle invalidation races in CatalogdMetaProvider cache >

[jira] [Assigned] (IMPALA-8667) Remove --pull_incremental_statistics flag (on by default)

[ https://issues.apache.org/jira/browse/IMPALA-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reassigned IMPALA-8667: --- Assignee: Todd Lipcon > Remove --pull_incremental_statistics flag (on by default) >

[jira] [Assigned] (IMPALA-7506) Support global INVALIDATE METADATA on fetch-on-demand impalad

[ https://issues.apache.org/jira/browse/IMPALA-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reassigned IMPALA-7506: --- Assignee: Todd Lipcon (was: Vuk Ercegovac) > Support global INVALIDATE METADATA on

[jira] [Created] (IMPALA-8673) Add query option to force plan hints for insert queries

Lars Volker created IMPALA-8673: --- Summary: Add query option to force plan hints for insert queries Key: IMPALA-8673 URL: https://issues.apache.org/jira/browse/IMPALA-8673 Project: IMPALA Issue

[jira] [Created] (IMPALA-8673) Add query option to force plan hints for insert queries

Lars Volker created IMPALA-8673: --- Summary: Add query option to force plan hints for insert queries Key: IMPALA-8673 URL: https://issues.apache.org/jira/browse/IMPALA-8673 Project: IMPALA Issue

[jira] [Commented] (IMPALA-6876) Entries in CatalogUsageMonitor are not cleared after invalidation

[ https://issues.apache.org/jira/browse/IMPALA-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866898#comment-16866898 ] Todd Lipcon commented on IMPALA-6876: - Looked at this a few minutes today. There are a few more

[jira] [Assigned] (IMPALA-7235) Allow the Statestore to shut down cleanly

[ https://issues.apache.org/jira/browse/IMPALA-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Mate reassigned IMPALA-7235: -- Assignee: (was: Tamas Mate) > Allow the Statestore to shut down cleanly >

[jira] [Work started] (IMPALA-7734) Catalog and Statestore memz page shows useless memory breakdown

[ https://issues.apache.org/jira/browse/IMPALA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7734 started by Tamas Mate. -- > Catalog and Statestore memz page shows useless memory breakdown >

[jira] [Resolved] (IMPALA-8459) Cannot delete impala/kudu table if backing kudu table dropped with local catalog

[ https://issues.apache.org/jira/browse/IMPALA-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved IMPALA-8459. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Cannot delete impala/kudu table if

[jira] [Resolved] (IMPALA-8459) Cannot delete impala/kudu table if backing kudu table dropped with local catalog

[ https://issues.apache.org/jira/browse/IMPALA-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved IMPALA-8459. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Cannot delete impala/kudu table if

[jira] [Commented] (IMPALA-8672) verification of read data failed with OpenSSL error in EVP_DecryptFinal decrypting while reading from scratch file

[ https://issues.apache.org/jira/browse/IMPALA-8672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866838#comment-16866838 ] Tim Armstrong commented on IMPALA-8672: --- Thanks. Just for context, we have seen this only on an

[jira] [Reopened] (IMPALA-8658) Populate required Ranger audit fields to be consistent with Hive

[ https://issues.apache.org/jira/browse/IMPALA-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya reopened IMPALA-8658: -- Accidentally clicked "resolved". > Populate required Ranger audit fields to be consistent with

[jira] [Resolved] (IMPALA-8658) Populate required Ranger audit fields to be consistent with Hive

[ https://issues.apache.org/jira/browse/IMPALA-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-8658. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Populate required Ranger audit fields

[jira] [Resolved] (IMPALA-8658) Populate required Ranger audit fields to be consistent with Hive

[ https://issues.apache.org/jira/browse/IMPALA-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-8658. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Populate required Ranger audit fields

[jira] [Resolved] (IMPALA-8599) Create a separate Maven module for query event hook API

[ https://issues.apache.org/jira/browse/IMPALA-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-8599. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Create a separate Maven module for

[jira] [Resolved] (IMPALA-8599) Create a separate Maven module for query event hook API

[ https://issues.apache.org/jira/browse/IMPALA-8599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-8599. -- Resolution: Fixed Fix Version/s: Impala 3.3.0 > Create a separate Maven module for

[jira] [Commented] (IMPALA-8671) Do not re-create a new instance of AuthorizationChecker with Ranger authorization

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

[jira] [Commented] (IMPALA-8542) Access trace collection for data cache

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

[jira] [Commented] (IMPALA-8599) Create a separate Maven module for query event hook API

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

[jira] [Commented] (IMPALA-8459) Cannot delete impala/kudu table if backing kudu table dropped with local catalog

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

[jira] [Resolved] (IMPALA-8542) Access trace collection for data cache

[ https://issues.apache.org/jira/browse/IMPALA-8542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved IMPALA-8542. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Access trace collection for data cache >

[jira] [Resolved] (IMPALA-8542) Access trace collection for data cache

[ https://issues.apache.org/jira/browse/IMPALA-8542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved IMPALA-8542. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Access trace collection for data cache >