[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&focusedCommentId=16663083#comment-16663083 ] Tim Armstrong commented on IMPALA-7371: --- [~bharathv] it looks like this was a meta

[jira] [Created] (IMPALA-7757) Add more info to signal handler log messages

Tim Armstrong created IMPALA-7757: - Summary: Add more info to signal handler log messages Key: IMPALA-7757 URL: https://issues.apache.org/jira/browse/IMPALA-7757 Project: IMPALA Issue Type: I

[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&focusedCommentId=16663964#comment-16663964 ] Tim Armstrong commented on IMPALA-6271: --- Filed IMPALA-7757. Please update as you s

[jira] [Commented] (IMPALA-7756) Create a "strict mode" for file parsing in debug builds

[ https://issues.apache.org/jira/browse/IMPALA-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663965#comment-16663965 ] Tim Armstrong commented on IMPALA-7756: --- Yeah the FILE_CHECK macros were intended

[jira] [Commented] (IMPALA-7756) Create a "strict mode" for file parsing in debug builds

[ https://issues.apache.org/jira/browse/IMPALA-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663969#comment-16663969 ] Tim Armstrong commented on IMPALA-7756: --- Maybe it's cheap enough to add an UNLIKEL

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

[ https://issues.apache.org/jira/browse/IMPALA-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7714 started by Tim Armstrong. - > Statestore::Subscriber::SetLastTopicVersionProcessed() crashed in > Atomic

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16664062#comment-16664062 ] Tim Armstrong commented on IMPALA-6374: --- [~sjc362000] finally took a look at this.

[jira] [Work stopped] (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 ] Work on IMPALA-7356 stopped by Tim Armstrong. - > Stress test for memory-based admission control > --

[jira] [Work stopped] (IMPALA-7648) Add tests for all cases where OOM is expected

[ https://issues.apache.org/jira/browse/IMPALA-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7648 stopped by Tim Armstrong. - > Add tests for all cases where OOM is expected > ---

[jira] [Assigned] (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:all-tabpanel ] Tim Armstrong reassigned IMPALA-7655: - Assignee: Paul Rogers > Codegen output for conditional functions (if,isnull, coalesce)

[jira] [Commented] (IMPALA-6433) Add read support for PageHeaderV2 to the parquet scanner

[ https://issues.apache.org/jira/browse/IMPALA-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664252#comment-16664252 ] Tim Armstrong commented on IMPALA-6433: --- [~boroknagyz] do you know if this is a de

[jira] [Assigned] (IMPALA-2607) S3: need to determine the right default for fs.s3a.connection.maximum

[ https://issues.apache.org/jira/browse/IMPALA-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-2607: - Assignee: (was: Sailesh Mukil) > S3: need to determine the right default for fs.s3a

[jira] [Commented] (IMPALA-7523) Planner Test failing with "Failed to assign regions to servers after 60000 millis."

[ https://issues.apache.org/jira/browse/IMPALA-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664302#comment-16664302 ] Tim Armstrong commented on IMPALA-7523: --- Happened in GVO: https://jenkins.impala.

[jira] [Updated] (IMPALA-7735) Expose admission control status in impala-shell

[ https://issues.apache.org/jira/browse/IMPALA-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7735: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Expose admission control status in impala-

[jira] [Updated] (IMPALA-7357) Consider lowering statestore update frequency further or adding jitter to admission controller

[ https://issues.apache.org/jira/browse/IMPALA-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7357: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Consider lowering statestore update freque

[jira] [Updated] (IMPALA-7351) Add memory estimates for plan nodes and sinks with missing estimates

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

[jira] [Updated] (IMPALA-7351) Add memory estimates for plan nodes and sinks with missing estimates

[ https://issues.apache.org/jira/browse/IMPALA-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7351: -- Labels: admission-control resource-management (was: resource-management) > Add memory estimat

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

[ https://issues.apache.org/jira/browse/IMPALA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664331#comment-16664331 ] Tim Armstrong commented on IMPALA-7353: --- DataSourceScanNode is the only one left p

[jira] [Updated] (IMPALA-7003) Support erasure-coding in impala

[ https://issues.apache.org/jira/browse/IMPALA-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7003: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Support erasure-coding in impala > ---

[jira] [Assigned] (IMPALA-7485) test_spilling_naaj hung on jenkins

[ https://issues.apache.org/jira/browse/IMPALA-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7485: - Assignee: Tim Armstrong > test_spilling_naaj hung on jenkins >

[jira] [Updated] (IMPALA-6352) TestTableSample took too long in recent tests

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

[jira] [Commented] (IMPALA-7766) Perform constant folding within an expression

[ https://issues.apache.org/jira/browse/IMPALA-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664453#comment-16664453 ] Tim Armstrong commented on IMPALA-7766: --- I think we should be folding subexpressio

[jira] [Resolved] (IMPALA-7485) test_spilling_naaj hung on jenkins

[ https://issues.apache.org/jira/browse/IMPALA-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7485. --- Resolution: Cannot Reproduce There was a cluster of hangs around this time related to IMPALA

[jira] [Resolved] (IMPALA-3706) Planner should set min/max per-node buffer pool reservations to optimize query performance

[ https://issues.apache.org/jira/browse/IMPALA-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3706. --- Resolution: Later Unclear if this is the right direction. Needs more thought. > Planner sho

[jira] [Updated] (IMPALA-1977) Slow cross join query - requires band join implementation

[ https://issues.apache.org/jira/browse/IMPALA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1977: -- Labels: (was: hang) > Slow cross join query - requires band join implementation > --

[jira] [Commented] (IMPALA-5921) Internal-UDF crashed

[ https://issues.apache.org/jira/browse/IMPALA-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664492#comment-16664492 ] Tim Armstrong commented on IMPALA-5921: --- [~attilaj][~jeszyb] this got neglected si

[jira] [Resolved] (IMPALA-1780) Catch exceptions thrown by UDFs

[ https://issues.apache.org/jira/browse/IMPALA-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-1780. --- Resolution: Later I think the proper solution here is some kind of sandboxing, rather than t

[jira] [Updated] (IMPALA-3950) Impala daemon crash because of C [libc.so.6+0x14a084] __memcpy_ssse3_back+0x1914 frame

[ https://issues.apache.org/jira/browse/IMPALA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3950: -- Labels: crash (was: ) > Impala daemon crash because of C [libc.so.6+0x14a084] > __memcpy_sss

[jira] [Resolved] (IMPALA-3950) Impala daemon crash because of C [libc.so.6+0x14a084] __memcpy_ssse3_back+0x1914 frame

[ https://issues.apache.org/jira/browse/IMPALA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3950. --- Resolution: Information Provided > Impala daemon crash because of C [libc.so.6+0x14a084] >

[jira] [Resolved] (IMPALA-414) Impala server cannot detect crash-restart failures reliably

[ https://issues.apache.org/jira/browse/IMPALA-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-414. -- Resolution: Duplicate I think this is describing IMPALA-2990 since we only need to detect cras

[jira] [Resolved] (IMPALA-5680) Avro scanner still crashing when HDFS seek fails

[ https://issues.apache.org/jira/browse/IMPALA-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-5680. --- Resolution: Cannot Reproduce > Avro scanner still crashing when HDFS seek fails > --

[jira] [Updated] (IMPALA-6762) DataStreamRecvr::SenderQueue::GetBatch encounters an exception doing a data_arrival_cv_.Wait(l)

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

[jira] [Updated] (IMPALA-6762) DataStreamRecvr::SenderQueue::GetBatch encounters an exception doing a data_arrival_cv_.Wait(l)

[ https://issues.apache.org/jira/browse/IMPALA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6762: -- Labels: crash (was: ) > DataStreamRecvr::SenderQueue::GetBatch encounters an exception doing

[jira] [Resolved] (IMPALA-6762) DataStreamRecvr::SenderQueue::GetBatch encounters an exception doing a data_arrival_cv_.Wait(l)

[ https://issues.apache.org/jira/browse/IMPALA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6762. --- Resolution: Cannot Reproduce I took another look and agree that it doesn't make sense - ther

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

[ https://issues.apache.org/jira/browse/IMPALA-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7714. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Statestore::Subscriber::SetLastTopicV

[jira] [Commented] (IMPALA-7738) Implement timeouts for HDFS calls

[ https://issues.apache.org/jira/browse/IMPALA-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665536#comment-16665536 ] Tim Armstrong commented on IMPALA-7738: --- [~joemcdonnell] more a curiousity than an

[jira] [Assigned] (IMPALA-4268) buffer more than a batch of rows at coordinator

[ https://issues.apache.org/jira/browse/IMPALA-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-4268: - Assignee: Bikramjeet Vig > buffer more than a batch of rows at coordinator > --

[jira] [Assigned] (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 reassigned IMPALA-7363: - Assignee: Pooja Nilangekar > Spurious error generated by sequence file scanner with wei

[jira] [Assigned] (IMPALA-7758) chars_formats dependent tables are created using the wrong LOCATION

[ https://issues.apache.org/jira/browse/IMPALA-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7758: - Assignee: David Knupp > chars_formats dependent tables are created using the wrong LOCA

[jira] [Created] (IMPALA-7774) Test JIRA, please ignore

Tim Armstrong created IMPALA-7774: - Summary: Test JIRA, please ignore Key: IMPALA-7774 URL: https://issues.apache.org/jira/browse/IMPALA-7774 Project: IMPALA Issue Type: Improvement

[jira] [Updated] (IMPALA-7774) Test JIRA, please ignore

[ https://issues.apache.org/jira/browse/IMPALA-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7774: -- Priority: Major (was: Critical) > Test JIRA, please ignore > > >

[jira] [Resolved] (IMPALA-7774) Test JIRA, please ignore

[ https://issues.apache.org/jira/browse/IMPALA-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7774. --- Resolution: Incomplete > Test JIRA, please ignore > > >

[jira] [Updated] (IMPALA-7446) Queries can spill earlier than necessary because of accumulation of free buffers and clean pages

[ https://issues.apache.org/jira/browse/IMPALA-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7446: -- Target Version: Impala 3.2.0 (was: Impala 3.1.0) > Queries can spill earlier than necessary b

[jira] [Commented] (IMPALA-6859) De-templatize RpcMgrTestBase

[ https://issues.apache.org/jira/browse/IMPALA-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665757#comment-16665757 ] Tim Armstrong commented on IMPALA-6859: --- Fixed by commit 5c541b960491ba9153371

[jira] [Resolved] (IMPALA-6859) De-templatize RpcMgrTestBase

[ https://issues.apache.org/jira/browse/IMPALA-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6859. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > De-templatize RpcMgrTestBase > --

[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&focusedCommentId=16665765#comment-16665765 ] Tim Armstrong commented on IMPALA-7586: --- I can pick this up for the release since

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

[ https://issues.apache.org/jira/browse/IMPALA-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7586: - Assignee: Tim Armstrong (was: Adrian Ng) > Incorrect results when querying primary = "

[jira] [Created] (IMPALA-7775) StatestoreSslTest crashed with mutex lock failed in pthread_mutex_lock: Invalid argument

Tim Armstrong created IMPALA-7775: - Summary: StatestoreSslTest crashed with mutex lock failed in pthread_mutex_lock: Invalid argument Key: IMPALA-7775 URL: https://issues.apache.org/jira/browse/IMPALA-7775

[jira] [Created] (IMPALA-7778) RCFile parser ignores escape characters

Tim Armstrong created IMPALA-7778: - Summary: RCFile parser ignores escape characters Key: IMPALA-7778 URL: https://issues.apache.org/jira/browse/IMPALA-7778 Project: IMPALA Issue Type: Bug

[jira] [Commented] (IMPALA-7778) RCFile parser ignores escape characters

[ https://issues.apache.org/jira/browse/IMPALA-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667423#comment-16667423 ] Tim Armstrong commented on IMPALA-7778: --- Found this while adding tests for IMPALA-

[jira] [Commented] (IMPALA-7778) RCFile parser ignores escape characters

[ https://issues.apache.org/jira/browse/IMPALA-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667427#comment-16667427 ] Tim Armstrong commented on IMPALA-7778: --- I'm not assigning this a high priority be

[jira] [Updated] (IMPALA-7778) RCFile parser ignores escape characters

[ https://issues.apache.org/jira/browse/IMPALA-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7778: -- Labels: correctness (was: ) > RCFile parser ignores escape characters > -

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

[ https://issues.apache.org/jira/browse/IMPALA-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7586: -- Summary: Incorrect results when querying primary = "\"" in Kudu and HBase (was: Incorrect res

[jira] [Work started] (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:all-tabpanel ] Work on IMPALA-7727 started by Tim Armstrong. - > failed compute stats child query status no longer propagates to parent quer

[jira] [Commented] (IMPALA-7565) Extends TAcceptQueueServer connection_setup_pool to be multi-threaded

[ https://issues.apache.org/jira/browse/IMPALA-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667572#comment-16667572 ] Tim Armstrong commented on IMPALA-7565: --- [~kwho] [~bikram.sngh91] [~lv] do we thin

[jira] [Work started] (IMPALA-7586) Incorrect results when querying primary = "\"" in Kudu and HBase

[ https://issues.apache.org/jira/browse/IMPALA-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7586 started by Tim Armstrong. - > Incorrect results when querying primary = "\"" in Kudu and HBase >

[jira] [Updated] (IMPALA-7662) test_parquet reads bad_magic_number.parquet without an error

[ https://issues.apache.org/jira/browse/IMPALA-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7662: -- Priority: Blocker (was: Critical) > test_parquet reads bad_magic_number.parquet without an er

[jira] [Commented] (IMPALA-2566) Result of casttochar() not handled properly in SQL operations

[ https://issues.apache.org/jira/browse/IMPALA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667575#comment-16667575 ] Tim Armstrong commented on IMPALA-2566: --- [~bikramjeet.vig] could you maybe take a

[jira] [Assigned] (IMPALA-2566) Result of casttochar() not handled properly in SQL operations

[ https://issues.apache.org/jira/browse/IMPALA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-2566: - Assignee: Bikramjeet Vig > Result of casttochar() not handled properly in SQL operation

[jira] [Updated] (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 ] Tim Armstrong updated IMPALA-6853: -- Target Version: Impala 3.2.0, Impala 2.13.0 (was: Impala 2.13.0, Impala 3.1.0) > COMPUTE STA

[jira] [Updated] (IMPALA-6671) Metadata operations that modify a table blocks topic updates for other unrelated operations

[ https://issues.apache.org/jira/browse/IMPALA-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6671: -- Target Version: Product Backlog > Metadata operations that modify a table blocks topic updates

[jira] [Updated] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-: -- Target Version: Impala 3.1.0 > Fail queries where the sum of offset and limit exceed the max v

[jira] [Updated] (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 ] Tim Armstrong updated IMPALA-6955: -- Fix Version/s: (was: Not Applicable) > Timeout when starting test_query_expiration custom

[jira] [Updated] (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 ] Tim Armstrong updated IMPALA-6955: -- Target Version: Impala 3.2.0 Labels: broken-build flaky (was: ) Priority

[jira] [Updated] (IMPALA-5765) Flaky tpc-ds data loading

[ https://issues.apache.org/jira/browse/IMPALA-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5765: -- Target Version: Impala 2.12.0, Product Backlog (was: Impala 2.12.0) Priority: Major

[jira] [Resolved] (IMPALA-5122) Impala and special character

[ https://issues.apache.org/jira/browse/IMPALA-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-5122. --- Resolution: Invalid Hi [~Tina], I'm going to close this purely because we don't track issu

[jira] [Updated] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5746: -- Target Version: Impala 3.2.0 (was: Product Backlog) > Remote fragments continue to hold onto

[jira] [Updated] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5746: -- Target Version: Product Backlog Per Michael's comment, it doesn't sound like we're going to ta

[jira] [Updated] (IMPALA-4018) Add support for SQL:2016 datetime templates/patterns/masks to CAST(... AS ... FORMAT )

[ https://issues.apache.org/jira/browse/IMPALA-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4018: -- Target Version: Product Backlog > Add support for SQL:2016 datetime templates/patterns/masks t

[jira] [Updated] (IMPALA-7282) Sentry privilege disappears after a catalog refresh

[ https://issues.apache.org/jira/browse/IMPALA-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7282: -- Target Version: Impala 3.2.0 > Sentry privilege disappears after a catalog refresh > -

[jira] [Updated] (IMPALA-6294) Concurrent hung with lots of spilling make slow progress due to blocking in DataStreamRecvr and DataStreamSender

[ https://issues.apache.org/jira/browse/IMPALA-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6294: -- Target Version: Impala 3.2.0 > Concurrent hung with lots of spilling make slow progress due to

[jira] [Updated] (IMPALA-7183) We should print the sender name when logging a report for an unknown status report on the coordinatior

[ https://issues.apache.org/jira/browse/IMPALA-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7183: -- Target Version: Impala 3.2.0 > We should print the sender name when logging a report for an un

[jira] [Updated] (IMPALA-7670) Drop table with a concurrent refresh throws ConcurrentModificationException

[ https://issues.apache.org/jira/browse/IMPALA-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7670: -- Target Version: Impala 3.2.0 > Drop table with a concurrent refresh throws ConcurrentModificat

[jira] [Updated] (IMPALA-6692) When partition exchange is followed by sort each sort node becomes a synchronization point across the cluster

[ https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6692: -- Target Version: Impala 3.2.0 > When partition exchange is followed by sort each sort node beco

[jira] [Updated] (IMPALA-6048) Queries make very slow progress and report WaitForRPC() stuck for too long

[ https://issues.apache.org/jira/browse/IMPALA-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6048: -- Target Version: Impala 3.2.0 > Queries make very slow progress and report WaitForRPC() stuck

[jira] [Updated] (IMPALA-6783) Rethink the end-to-end queuing at KrpcDataStreamReceiver

[ https://issues.apache.org/jira/browse/IMPALA-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6783: -- Target Version: Impala 3.2.0 > Rethink the end-to-end queuing at KrpcDataStreamReceiver >

[jira] [Updated] (IMPALA-6808) Impala python code should be installed into infra/python/env like other packages

[ https://issues.apache.org/jira/browse/IMPALA-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6808: -- Target Version: Product Backlog Priority: Major (was: Critical) I'm just going to c

[jira] [Updated] (IMPALA-7523) Planner Test failing with "Failed to assign regions to servers after 60000 millis."

[ https://issues.apache.org/jira/browse/IMPALA-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7523: -- Target Version: Impala 3.2.0 > Planner Test failing with "Failed to assign regions to servers

[jira] [Updated] (IMPALA-7003) Support erasure-coding in impala

[ https://issues.apache.org/jira/browse/IMPALA-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7003: -- Target Version: Product Backlog (was: Impala 3.2.0) I'll just put this on backlog until there

[jira] [Updated] (IMPALA-6194) Ensure all fragment instances notice cancellation

[ https://issues.apache.org/jira/browse/IMPALA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6194: -- Target Version: Impala 3.2.0 > Ensure all fragment instances notice cancellation > ---

[jira] [Updated] (IMPALA-7742) User names in Sentry are now case sensitive

[ https://issues.apache.org/jira/browse/IMPALA-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7742: -- Target Version: Impala 3.1.0 > User names in Sentry are now case sensitive > -

[jira] [Updated] (IMPALA-6890) split-hbase.sh: Can't get master address from ZooKeeper; znode data == null

[ https://issues.apache.org/jira/browse/IMPALA-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6890: -- Target Version: Impala 3.1.0, Impala 2.13.0 (was: Impala 2.13.0) > split-hbase.sh: Can't get

[jira] [Updated] (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 ] Tim Armstrong updated IMPALA-7070: -- Fix Version/s: (was: Impala 3.1.0) > Failed test: > query_test.test_nested_types.TestParq

[jira] [Updated] (IMPALA-6890) split-hbase.sh: Can't get master address from ZooKeeper; znode data == null

[ https://issues.apache.org/jira/browse/IMPALA-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6890: -- Priority: Critical (was: Blocker) > split-hbase.sh: Can't get master address from ZooKeeper;

[jira] [Updated] (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 ] Tim Armstrong updated IMPALA-7070: -- Target Version: Impala 3.1.0 > Failed test: > query_test.test_nested_types.TestParquetArrayEn

[jira] [Resolved] (IMPALA-2680) Align un-aligned memory copies

[ https://issues.apache.org/jira/browse/IMPALA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2680. --- Resolution: Won't Fix I don't think this actually makes sense, we've generally see that it's

[jira] [Resolved] (IMPALA-7662) test_parquet reads bad_magic_number.parquet without an error

[ https://issues.apache.org/jira/browse/IMPALA-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7662. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > test_parquet reads bad_magic_number.p

[jira] [Assigned] (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:all-tabpanel ] Tim Armstrong reassigned IMPALA-7727: - Assignee: bharath v (was: Tim Armstrong) > failed compute stats child query status no

[jira] [Updated] (IMPALA-7782) discrepancy in results with a subquery containing an agg that produces an empty set

[ https://issues.apache.org/jira/browse/IMPALA-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7782: -- Target Version: Impala 3.1.0 > discrepancy in results with a subquery containing an agg that p

[jira] [Work started] (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 ] Work on IMPALA-6374 started by Tim Armstrong. - > test tpcds-q98.test has some incorrect data >

[jira] [Commented] (IMPALA-7782) discrepancy in results with a subquery containing an agg that produces an empty set

[ https://issues.apache.org/jira/browse/IMPALA-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668899#comment-16668899 ] Tim Armstrong commented on IMPALA-7782: --- Looks like a bad rewrite in the planner.

[jira] [Commented] (IMPALA-7775) StatestoreSslTest crashed with mutex lock failed in pthread_mutex_lock: Invalid argument

[ https://issues.apache.org/jira/browse/IMPALA-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668985#comment-16668985 ] Tim Armstrong commented on IMPALA-7775: --- This reproduces on my dev environment if

[jira] [Commented] (IMPALA-7775) StatestoreSslTest crashed with mutex lock failed in pthread_mutex_lock: Invalid argument

[ https://issues.apache.org/jira/browse/IMPALA-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669060#comment-16669060 ] Tim Armstrong commented on IMPALA-7775: --- It looks like the heartbeat thread crashe

[jira] [Resolved] (IMPALA-3473) Flaky Test Failure: KuduTableSinkTest.TestInsertJustKey

[ https://issues.apache.org/jira/browse/IMPALA-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3473. --- Resolution: Cannot Reproduce > Flaky Test Failure: KuduTableSinkTest.TestInsertJustKey > ---

[jira] [Resolved] (IMPALA-3598) Timestamp casting is inconsistent

[ https://issues.apache.org/jira/browse/IMPALA-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3598. --- Resolution: Fixed > Timestamp casting is inconsistent > - >

[jira] [Updated] (IMPALA-1977) Slow cross join query - requires band join implementation

[ https://issues.apache.org/jira/browse/IMPALA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1977: -- Issue Type: Improvement (was: Bug) > Slow cross join query - requires band join implementatio

[jira] [Updated] (IMPALA-5847) Some query options do not work as expected in .test files

[ https://issues.apache.org/jira/browse/IMPALA-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5847: -- Issue Type: Improvement (was: Bug) > Some query options do not work as expected in .test file

[jira] [Assigned] (IMPALA-558) HS2::FetchResults sets hasMoreRows in many cases where no more rows are to be returned

[ https://issues.apache.org/jira/browse/IMPALA-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-558: Assignee: (was: Alexander Behm) > HS2::FetchResults sets hasMoreRows in many cases whe

[jira] [Assigned] (IMPALA-532) Impala should tolerate bad locale settings.

[ https://issues.apache.org/jira/browse/IMPALA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-532: Assignee: (was: Henry Robinson) > Impala should tolerate bad locale settings. > --

[jira] [Resolved] (IMPALA-580) Inconsistent or blank fileFormats values passed to CM

[ https://issues.apache.org/jira/browse/IMPALA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-580. -- Resolution: Cannot Reproduce > Inconsistent or blank fileFormats values passed to CM >

<    5   6   7   8   9   10   11   12   13   14   >