[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] [Created] (IMPALA-7750) Additional FE optimizations for CASE expressions

Paul Rogers created IMPALA-7750: --- Summary: Additional FE optimizations for CASE expressions Key: IMPALA-7750 URL: https://issues.apache.org/jira/browse/IMPALA-7750 Project: IMPALA Issue Type:

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

[ https://issues.apache.org/jira/browse/IMPALA-7740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni closed IMPALA-7740. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Incorrect doc description for nvl2() >

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

Tim Armstrong created IMPALA-7749: - Summary: Merge aggregation node memory estimate is incorrectly influenced by limit Key: IMPALA-7749 URL: https://issues.apache.org/jira/browse/IMPALA-7749 Project:

[jira] [Commented] (IMPALA-7475) Explicitly document perf consequences of setting mem_limit

[ https://issues.apache.org/jira/browse/IMPALA-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661508#comment-16661508 ] Alex Rodoni commented on IMPALA-7475: - [~tarmstrong] If you write in google doc, I can convert it to

[jira] [Assigned] (IMPALA-7475) Explicitly document perf consequences of setting mem_limit

[ https://issues.apache.org/jira/browse/IMPALA-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7475: - Assignee: Tim Armstrong (was: Alex Rodoni) > Explicitly document perf consequences of

[jira] [Commented] (IMPALA-7475) Explicitly document perf consequences of setting mem_limit

[ https://issues.apache.org/jira/browse/IMPALA-7475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661498#comment-16661498 ] Tim Armstrong commented on IMPALA-7475: --- Thanks for the pointer. I'll look at adding it there. >

[jira] [Updated] (IMPALA-7692) Profile averages not computed for Exchange InactiveTotalTime TIME_NS counter

[ https://issues.apache.org/jira/browse/IMPALA-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7692: -- Labels: observability (was: ) > Profile averages not computed for Exchange InactiveTotalTime

[jira] [Commented] (IMPALA-7746) test_corrupt_footer_len_incr fails for asan tests

[ https://issues.apache.org/jira/browse/IMPALA-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661478#comment-16661478 ] Tim Armstrong commented on IMPALA-7746: --- This looks like IMPALA-7662. The error message comes from

[jira] [Resolved] (IMPALA-7746) test_corrupt_footer_len_incr fails for asan tests

[ https://issues.apache.org/jira/browse/IMPALA-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7746. --- Resolution: Duplicate > test_corrupt_footer_len_incr fails for asan tests >

[jira] [Resolved] (IMPALA-7668) close() URLClassLoaders after usage.

[ https://issues.apache.org/jira/browse/IMPALA-7668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v resolved IMPALA-7668. --- Resolution: Fixed > close() URLClassLoaders after usage. > > >

[jira] [Updated] (IMPALA-7668) close() URLClassLoaders after usage.

[ https://issues.apache.org/jira/browse/IMPALA-7668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7668: -- Affects Version/s: Impala 3.1.0 Impala 2.12.0 > close() URLClassLoaders after

[jira] [Updated] (IMPALA-3185) Toolchain should verify download hash

[ https://issues.apache.org/jira/browse/IMPALA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Apple updated IMPALA-3185: -- Summary: Toolchain should verify download hash (was: Toolchain should not verify download hash) >

[jira] [Resolved] (IMPALA-7661) test_reconnect is flaky in asan

[ https://issues.apache.org/jira/browse/IMPALA-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7661. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > test_reconnect is flaky in asan >

[jira] [Assigned] (IMPALA-7661) test_reconnect is flaky in asan

[ https://issues.apache.org/jira/browse/IMPALA-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7661: - Assignee: Tianyi Wang > test_reconnect is flaky in asan >

[jira] [Commented] (IMPALA-7661) test_reconnect is flaky in asan

[ https://issues.apache.org/jira/browse/IMPALA-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661471#comment-16661471 ] Tim Armstrong commented on IMPALA-7661: --- IMPALA-7661: Increase the sleep time in

[jira] [Updated] (IMPALA-3834) Test and fix invalid data handling in compressed text scanners

[ https://issues.apache.org/jira/browse/IMPALA-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3834: -- Priority: Major (was: Critical) > Test and fix invalid data handling in compressed text

[jira] [Assigned] (IMPALA-1821) Casting scenarios with invalid/inconsistent results

[ https://issues.apache.org/jira/browse/IMPALA-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-1821: - Assignee: (was: Alexander Behm) > Casting scenarios with invalid/inconsistent

[jira] [Updated] (IMPALA-3185) Toolchain should not verify download hash

[ https://issues.apache.org/jira/browse/IMPALA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3185: -- Summary: Toolchain should not verify download hash (was: Toolchain should not trust

[jira] [Commented] (IMPALA-3185) Toolchain should not trust downloads

[ https://issues.apache.org/jira/browse/IMPALA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661461#comment-16661461 ] Tim Armstrong commented on IMPALA-3185: --- We download everything over https now afaik so this is

[jira] [Reopened] (IMPALA-7070) Failed test: query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays on S3

[ https://issues.apache.org/jira/browse/IMPALA-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker reopened IMPALA-7070: - > Failed test: >

[jira] [Updated] (IMPALA-3185) Toolchain should not trust downloads

[ https://issues.apache.org/jira/browse/IMPALA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3185: -- Issue Type: Improvement (was: Bug) > Toolchain should not trust downloads >

[jira] [Updated] (IMPALA-6662) Make stress test resilient to hangs due to client crashes

[ https://issues.apache.org/jira/browse/IMPALA-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6662: -- Priority: Major (was: Critical) > Make stress test resilient to hangs due to client crashes

[jira] [Work stopped] (IMPALA-6326) segfault during impyla HiveServer2Cursor.cancel_operation() over SSL

[ https://issues.apache.org/jira/browse/IMPALA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-6326 stopped by Tim Armstrong. - > segfault during impyla HiveServer2Cursor.cancel_operation() over SSL >

[jira] [Work stopped] (IMPALA-6662) Make stress test resilient to hangs due to client crashes

[ https://issues.apache.org/jira/browse/IMPALA-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-6662 stopped by Tim Armstrong. - > Make stress test resilient to hangs due to client crashes >

[jira] [Assigned] (IMPALA-6662) Make stress test resilient to hangs due to client crashes

[ https://issues.apache.org/jira/browse/IMPALA-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6662: - Assignee: (was: Sailesh Mukil) > Make stress test resilient to hangs due to client

[jira] [Updated] (IMPALA-6662) Make stress test resilient to hangs due to client crashes

[ https://issues.apache.org/jira/browse/IMPALA-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6662: -- Target Version: Product Backlog > Make stress test resilient to hangs due to client crashes >

[jira] [Commented] (IMPALA-6814) query_test.test_queries.TestQueriesTextTables.test_strict_mode failing on remote clusters

[ https://issues.apache.org/jira/browse/IMPALA-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661447#comment-16661447 ] Tim Armstrong commented on IMPALA-6814: --- [~dknupp] is this still an issue? >

[jira] [Commented] (IMPALA-7586) Incorrect results when querying primary = "\"" in Kudu

[ https://issues.apache.org/jira/browse/IMPALA-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661437#comment-16661437 ] Tim Armstrong commented on IMPALA-7586: --- [~vercego][~adrian.ng] > Incorrect results when querying

[jira] [Commented] (IMPALA-7696) llvm crash in custom cluster test

[ https://issues.apache.org/jira/browse/IMPALA-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661435#comment-16661435 ] Tim Armstrong commented on IMPALA-7696: --- This looks a bit like IMPALA-7714 in that it may have

[jira] [Updated] (IMPALA-7696) llvm crash in custom cluster test

[ https://issues.apache.org/jira/browse/IMPALA-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7696: -- Attachment: 07015206-bbc7-414c-b9e5f0a6-3f8194e3.dmp_dumped > llvm crash in custom cluster

[jira] [Commented] (IMPALA-7696) llvm crash in custom cluster test

[ https://issues.apache.org/jira/browse/IMPALA-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661430#comment-16661430 ] Tim Armstrong commented on IMPALA-7696: --- Just attached the full minidump output:

[jira] [Commented] (IMPALA-7668) close() URLClassLoaders after usage.

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

[jira] [Updated] (IMPALA-3113) test_permanent_udfs.py takes 13 minutes

[ https://issues.apache.org/jira/browse/IMPALA-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3113: -- Target Version: Product Backlog (was: Impala 2.7.0) > test_permanent_udfs.py takes 13

[jira] [Updated] (IMPALA-1964) Improve Write Performance

[ https://issues.apache.org/jira/browse/IMPALA-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1964: -- Priority: Major (was: Critical) > Improve Write Performance > - > >

[jira] [Updated] (IMPALA-6354) Consider using Guava LoadingCache to cache metadata objects opposed to a ConcurrentHashMap

[ https://issues.apache.org/jira/browse/IMPALA-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6354: -- Component/s: Catalog > Consider using Guava LoadingCache to cache metadata objects opposed to

[jira] [Updated] (IMPALA-2648) catalogd crashes when serialized messages are over 2 GB

[ https://issues.apache.org/jira/browse/IMPALA-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2648: -- Component/s: Catalog > catalogd crashes when serialized messages are over 2 GB >

[jira] [Updated] (IMPALA-2029) Impala in CDH 5.2.0 fails to compile with hadoop 2.7

[ https://issues.apache.org/jira/browse/IMPALA-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2029: -- Priority: Major (was: Critical) > Impala in CDH 5.2.0 fails to compile with hadoop 2.7 >

[jira] [Resolved] (IMPALA-2652) tests/metadata/test_ddl.py test_create_drop_data_src fails when run a second time

[ https://issues.apache.org/jira/browse/IMPALA-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2652. --- Resolution: Duplicate > tests/metadata/test_ddl.py test_create_drop_data_src fails when run

[jira] [Updated] (IMPALA-3124) Add external metadata notification mechanisms to Impala

[ https://issues.apache.org/jira/browse/IMPALA-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3124: -- Priority: Major (was: Critical) > Add external metadata notification mechanisms to Impala >

[jira] [Resolved] (IMPALA-3959) data loading jenkins jobs don't save test logs

[ https://issues.apache.org/jira/browse/IMPALA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3959. --- Resolution: Invalid This is a cloudera infra issue > data loading jenkins jobs don't save

[jira] [Updated] (IMPALA-3234) Catalog should send incremental metadata changes to Impalads

[ https://issues.apache.org/jira/browse/IMPALA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3234: -- Priority: Major (was: Critical) > Catalog should send incremental metadata changes to

[jira] [Updated] (IMPALA-3966) Create tests for leap second coming up end of year 2016

[ https://issues.apache.org/jira/browse/IMPALA-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3966: -- Priority: Major (was: Critical) > Create tests for leap second coming up end of year 2016 >

[jira] [Commented] (IMPALA-3966) Create tests for leap second coming up end of year 2016

[ https://issues.apache.org/jira/browse/IMPALA-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661412#comment-16661412 ] Tim Armstrong commented on IMPALA-3966: --- [~dknupp] maybe [~attilaj] should take a look at this to

[jira] [Updated] (IMPALA-4005) generate_statements method in generate_schema_statements.py needs refactoring

[ https://issues.apache.org/jira/browse/IMPALA-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4005: -- Priority: Major (was: Critical) > generate_statements method in

[jira] [Updated] (IMPALA-4005) generate_statements method in generate_schema_statements.py needs refactoring

[ https://issues.apache.org/jira/browse/IMPALA-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4005: -- Issue Type: Improvement (was: Bug) > generate_statements method in

[jira] [Updated] (IMPALA-3968) qgen: create query profile emphasizing first_value / last_value testing

[ https://issues.apache.org/jira/browse/IMPALA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3968: -- Priority: Major (was: Critical) > qgen: create query profile emphasizing first_value /

[jira] [Updated] (IMPALA-4010) Test & fix invalid data handling in compressed text scanners

[ https://issues.apache.org/jira/browse/IMPALA-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4010: -- Priority: Major (was: Critical) > Test & fix invalid data handling in compressed text

[jira] [Commented] (IMPALA-6138) Thread creation failure in TAcceptQueueServer may cause crash

[ https://issues.apache.org/jira/browse/IMPALA-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661407#comment-16661407 ] Tim Armstrong commented on IMPALA-6138: --- I think with KRPC the odds of seeing this are much lower.

[jira] [Updated] (IMPALA-6138) Thread creation failure in TAcceptQueueServer may cause crash

[ https://issues.apache.org/jira/browse/IMPALA-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6138: -- Priority: Major (was: Critical) > Thread creation failure in TAcceptQueueServer may cause

[jira] [Resolved] (IMPALA-6167) Single quotes inside double quotes drop data

[ https://issues.apache.org/jira/browse/IMPALA-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6167. --- Resolution: Duplicate This produces the expected result on master. Pretty sure this was a

[jira] [Updated] (IMPALA-6266) Runtime filters should not have non-deterministic expression on consumer side

[ https://issues.apache.org/jira/browse/IMPALA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6266: -- Priority: Major (was: Critical) > Runtime filters should not have non-deterministic

[jira] [Updated] (IMPALA-6266) Runtime filters should not have non-deterministic expression on consumer side

[ https://issues.apache.org/jira/browse/IMPALA-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6266: -- Target Version: Product Backlog > Runtime filters should not have non-deterministic

[jira] [Updated] (IMPALA-6374) test tpcds-q98.test has some incorrect data

[ https://issues.apache.org/jira/browse/IMPALA-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6374: -- Summary: test tpcds-q98.test has some incorrect data (was: 3) > test tpcds-q98.test has

[jira] [Updated] (IMPALA-6784) Upgrade gperftools to 2.6.90 or beyond

[ https://issues.apache.org/jira/browse/IMPALA-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6784: -- Priority: Major (was: Critical) > Upgrade gperftools to 2.6.90 or beyond >

[jira] [Updated] (IMPALA-6784) Upgrade gperftools to 2.6.90 or beyond

[ https://issues.apache.org/jira/browse/IMPALA-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6784: -- Priority: Critical (was: Major) > Upgrade gperftools to 2.6.90 or beyond >

[jira] [Resolved] (IMPALA-6925) 'load-data functional-query exhaustive' failed: exception in load-data worker thread

[ https://issues.apache.org/jira/browse/IMPALA-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6925. --- Resolution: Cannot Reproduce > 'load-data functional-query exhaustive' failed: exception in

[jira] [Updated] (IMPALA-1628) Improve synchronization protocol in the catalog

[ https://issues.apache.org/jira/browse/IMPALA-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1628: -- Priority: Major (was: Critical) > Improve synchronization protocol in the catalog >

[jira] [Updated] (IMPALA-1876) add memory leak checking for cluster processes

[ https://issues.apache.org/jira/browse/IMPALA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1876: -- Summary: add memory leak checking for cluster processes (was: add memory leak checking for

[jira] [Updated] (IMPALA-1876) make sure that the memory leak check is working well

[ https://issues.apache.org/jira/browse/IMPALA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1876: -- Priority: Major (was: Critical) > make sure that the memory leak check is working well >

[jira] [Updated] (IMPALA-1876) add memory leak checking for cluster process

[ https://issues.apache.org/jira/browse/IMPALA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1876: -- Summary: add memory leak checking for cluster process (was: make sure that the memory leak

[jira] [Updated] (IMPALA-1876) make sure that the memory leak check is working well

[ https://issues.apache.org/jira/browse/IMPALA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1876: -- Issue Type: Improvement (was: Bug) > make sure that the memory leak check is working well >

[jira] [Commented] (IMPALA-402) Add test for dynamic partition expr involving rand()

[ https://issues.apache.org/jira/browse/IMPALA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661387#comment-16661387 ] Tim Armstrong commented on IMPALA-402: -- I can't reproduce this on master either with clustered or

[jira] [Updated] (IMPALA-402) Add test for dynamic partition expr involving rand()

[ https://issues.apache.org/jira/browse/IMPALA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-402: - Labels: (was: crash) > Add test for dynamic partition expr involving rand() >

[jira] [Updated] (IMPALA-402) Add test for dynamic partition expr involving rand()

[ https://issues.apache.org/jira/browse/IMPALA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-402: - Priority: Major (was: Critical) > Add test for dynamic partition expr involving rand() >

[jira] [Updated] (IMPALA-402) Add test for dynamic partition expr involving rand()

[ https://issues.apache.org/jira/browse/IMPALA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-402: - Summary: Add test for dynamic partition expr involving rand() (was: Dynamic partition expr

[jira] [Updated] (IMPALA-402) Add test for dynamic partition expr involving rand()

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

[jira] [Updated] (IMPALA-402) Dynamic partition expr involving rand() is evaluated only once

[ https://issues.apache.org/jira/browse/IMPALA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-402: - Issue Type: Improvement (was: Bug) > Dynamic partition expr involving rand() is evaluated only

[jira] [Resolved] (IMPALA-2442) Document rebase process and cherry-pick sync from release process

[ https://issues.apache.org/jira/browse/IMPALA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2442. --- Resolution: Won't Do No longer appears to be relevant > Document rebase process and

[jira] [Resolved] (IMPALA-2395) Document how to run Impala compat on RHEL7 static RM

[ https://issues.apache.org/jira/browse/IMPALA-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2395. --- Resolution: Won't Do No longer appears to be relevant > Document how to run Impala compat

[jira] [Resolved] (IMPALA-2394) Validate RHEL7 cluster, static RM

[ https://issues.apache.org/jira/browse/IMPALA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2394. --- Resolution: Won't Do No longer appears to be relevant > Validate RHEL7 cluster, static RM

[jira] [Resolved] (IMPALA-2393) Document how to show RHEL7 integration test status

[ https://issues.apache.org/jira/browse/IMPALA-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2393. --- Resolution: Invalid Appears to be a cloudera-specific JIRA > Document how to show RHEL7

[jira] [Updated] (IMPALA-2522) Improve the reliability and effectiveness of ETL

[ https://issues.apache.org/jira/browse/IMPALA-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2522: -- Priority: Major (was: Critical) > Improve the reliability and effectiveness of ETL >

[jira] [Updated] (IMPALA-1985) Auditing Does not Work Correctly With Redaction in HS2

[ https://issues.apache.org/jira/browse/IMPALA-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1985: -- Priority: Major (was: Critical) > Auditing Does not Work Correctly With Redaction in HS2 >

[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: -- Priority: Major (was: Critical) > Check memory limits in RowBatch constructor and

[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=16659482#comment-16659482 ] Paul Rogers edited comment on IMPALA-7655 at 10/23/18 10:12 PM: 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: -- Issue Type: Improvement (was: Bug) > Check memory limits in RowBatch constructor and

[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: -- Priority: Minor (was: Major) > Check memory limits in RowBatch constructor and

[jira] [Updated] (IMPALA-2214) Add some parquet-related testing

[ https://issues.apache.org/jira/browse/IMPALA-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2214: -- Priority: Major (was: Critical) > Add some parquet-related testing >

[jira] [Updated] (IMPALA-2138) Get rid of unused columns by upstream operators at points of materialization

[ https://issues.apache.org/jira/browse/IMPALA-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2138: -- Priority: Major (was: Critical) > Get rid of unused columns by upstream operators at points

[jira] [Updated] (IMPALA-2619) create scripts for reliable core file debugging

[ https://issues.apache.org/jira/browse/IMPALA-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2619: -- Priority: Major (was: Critical) > create scripts for reliable core file debugging >

[jira] [Updated] (IMPALA-2756) Rethink UDF interfaces

[ https://issues.apache.org/jira/browse/IMPALA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2756: -- Priority: Major (was: Critical) > Rethink UDF interfaces > -- > >

[jira] [Updated] (IMPALA-2875) Optimize subplans when the following plan nodes do not require parent rows.

[ https://issues.apache.org/jira/browse/IMPALA-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2875: -- Priority: Major (was: Critical) > Optimize subplans when the following plan nodes do not

[jira] [Updated] (IMPALA-2807) During insert operation impala creates too many files for a table size < block size

[ https://issues.apache.org/jira/browse/IMPALA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2807: -- Priority: Major (was: Critical) > During insert operation impala creates too many files for

[jira] [Updated] (IMPALA-2756) Rethink UDF interfaces

[ https://issues.apache.org/jira/browse/IMPALA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2756: -- Issue Type: Improvement (was: Bug) > Rethink UDF interfaces > -- > >

[jira] [Updated] (IMPALA-3127) Decouple partitions from tables

[ https://issues.apache.org/jira/browse/IMPALA-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3127: -- Priority: Major (was: Critical) > Decouple partitions from tables >

[jira] [Updated] (IMPALA-3060) Supports IS [NOT] NULL feature for complex types

[ https://issues.apache.org/jira/browse/IMPALA-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3060: -- Priority: Major (was: Critical) > Supports IS [NOT] NULL feature for complex types >

[jira] [Updated] (IMPALA-3791) Code coverage build is not generating C++ coverage information

[ https://issues.apache.org/jira/browse/IMPALA-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3791: -- Priority: Major (was: Critical) > Code coverage build is not generating C++ coverage

[jira] [Updated] (IMPALA-3273) LEAD and LAG do not support a column for the default value

[ https://issues.apache.org/jira/browse/IMPALA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3273: -- Priority: Major (was: Critical) > LEAD and LAG do not support a column for the default value

[jira] [Resolved] (IMPALA-3792) Test failures not obvious through Jenkins

[ https://issues.apache.org/jira/browse/IMPALA-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3792. --- Resolution: Invalid This is mostly about cloudera infrastructure. There was some recent

[jira] [Commented] (IMPALA-6062) Frontend tests need to handle hadoop 3 error messages

[ https://issues.apache.org/jira/browse/IMPALA-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661358#comment-16661358 ] Tim Armstrong commented on IMPALA-6062: --- The below commit added a hack to insert quotes to the

[jira] [Resolved] (IMPALA-6062) Frontend tests need to handle hadoop 3 error messages

[ https://issues.apache.org/jira/browse/IMPALA-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6062. --- Resolution: Fixed Fix Version/s: Impala 3.0 We're running against hadoop 3 so this

[jira] [Updated] (IMPALA-6119) Inconsistent file metadata updates when multiple partitions point to the same path

[ https://issues.apache.org/jira/browse/IMPALA-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6119: -- Target Version: Product Backlog > Inconsistent file metadata updates when multiple partitions

[jira] [Updated] (IMPALA-6119) Inconsistent file metadata updates when multiple partitions point to the same path

[ https://issues.apache.org/jira/browse/IMPALA-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6119: -- Priority: Major (was: Critical) > Inconsistent file metadata updates when multiple

[jira] [Resolved] (IMPALA-4130) Severe lock contention introduced by Log4j causing severe slow down in planning and other phases

[ https://issues.apache.org/jira/browse/IMPALA-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-4130. --- Resolution: Cannot Reproduce > Severe lock contention introduced by Log4j causing severe

[jira] [Resolved] (IMPALA-5103) gerrit-verify-dryrun can spin off competing Jobs

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

[jira] [Updated] (IMPALA-4244) Impala should strip all strings from log output unless explicitly configured to do so

[ https://issues.apache.org/jira/browse/IMPALA-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4244: -- Priority: Major (was: Critical) > Impala should strip all strings from log output unless

[jira] [Updated] (IMPALA-4244) Impala should strip all strings from log output unless explicitly configured to do so

[ https://issues.apache.org/jira/browse/IMPALA-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4244: -- Target Version: Product Backlog > Impala should strip all strings from log output unless

[jira] [Updated] (IMPALA-4244) Impala should strip all strings from log output unless explicitly configured to do so

[ https://issues.apache.org/jira/browse/IMPALA-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4244: -- Issue Type: Improvement (was: Bug) > Impala should strip all strings from log output unless

[jira] [Resolved] (IMPALA-4451) Impala crashes on thread creation failure when hitting ulimit

[ https://issues.apache.org/jira/browse/IMPALA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-4451. --- Resolution: Duplicate > Impala crashes on thread creation failure when hitting ulimit >

  1   2   >