[jira] [Resolved] (IMPALA-7349) Automatically choose mem_limit based on estimate, clamped to range

[ https://issues.apache.org/jira/browse/IMPALA-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7349. Resolution: Fixed Fix Version/s: Impala 3.1.0 https://github.com/apache/impala/comm

[jira] [Commented] (IMPALA-3600) Add missing admission control test coverage

[ https://issues.apache.org/jira/browse/IMPALA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642662#comment-16642662 ] Bikramjeet Vig commented on IMPALA-3600: added some for of this "Changing pool c

[jira] [Commented] (IMPALA-3600) Add missing admission control test coverage

[ https://issues.apache.org/jira/browse/IMPALA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644115#comment-16644115 ] Bikramjeet Vig commented on IMPALA-3600: IMPALA-6969 and IMPALA-3134 added cove

[jira] [Comment Edited] (IMPALA-3600) Add missing admission control test coverage

[ https://issues.apache.org/jira/browse/IMPALA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642662#comment-16642662 ] Bikramjeet Vig edited comment on IMPALA-3600 at 10/9/18 9:21 PM: -

[jira] [Assigned] (IMPALA-7684) Fix Admission result string in printed in the query profile

[ https://issues.apache.org/jira/browse/IMPALA-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7684: -- Assignee: Bikramjeet Vig > Fix Admission result string in printed in the query profil

[jira] [Created] (IMPALA-7684) Fix Admission result string

Bikramjeet Vig created IMPALA-7684: -- Summary: Fix Admission result string Key: IMPALA-7684 URL: https://issues.apache.org/jira/browse/IMPALA-7684 Project: IMPALA Issue Type: Bug Co

[jira] [Updated] (IMPALA-7684) Fix Admission result string in printed in the query profile

[ https://issues.apache.org/jira/browse/IMPALA-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7684: --- Summary: Fix Admission result string in printed in the query profile (was: Fix Admission re

[jira] [Work started] (IMPALA-7690) TestAdmissionController.test_pool_config_change_while_queued fails on centos6

[ https://issues.apache.org/jira/browse/IMPALA-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7690 started by Bikramjeet Vig. -- > TestAdmissionController.test_pool_config_change_while_queued fails on cen

[jira] [Resolved] (IMPALA-7690) TestAdmissionController.test_pool_config_change_while_queued fails on centos6

[ https://issues.apache.org/jira/browse/IMPALA-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7690. Resolution: Fixed Fix Version/s: Impala 3.1.0 > TestAdmissionController.test_pool_c

[jira] [Commented] (IMPALA-7697) Query gets erased before reporting ExecSummary

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650672#comment-16650672 ] Bikramjeet Vig commented on IMPALA-7697: [~kwho] I haven't looked at this yet, b

[jira] [Updated] (IMPALA-7697) Query gets erased before the client gets a chance to call get_log to fetch the error string

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7697: --- Summary: Query gets erased before the client gets a chance to call get_log to fetch the erro

[jira] [Updated] (IMPALA-7697) Query gets erased before the client gets a chance to call get_log to fetch the error string

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7697: --- Description: In a recent build, certain queries went missing from the ImpalaServer::query_l

[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&focusedCommentId=16654512#comment-16654512 ] Bikramjeet Vig commented on IMPALA-7696: Since there really is no info in the lo

[jira] [Commented] (IMPALA-7697) Query gets erased before the client gets a chance to call get_log to fetch the error string

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656153#comment-16656153 ] Bikramjeet Vig commented on IMPALA-7697: I looked into the logs and this seems l

[jira] [Resolved] (IMPALA-7684) Fix Admission result string in printed in the query profile

[ https://issues.apache.org/jira/browse/IMPALA-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7684. Resolution: Fixed Fix Version/s: Impala 3.1.0 [https://github.com/apache/impala/com

[jira] [Updated] (IMPALA-7697) Query gets erased before the client gets a chance to call get_log to fetch the error string

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7697: --- Labels: broken-build flaky-test (was: broken-build) > Query gets erased before the client g

[jira] [Resolved] (IMPALA-7699) TestSpillingNoDebugActionDimensions fails earlier than expected

[ https://issues.apache.org/jira/browse/IMPALA-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7699. Resolution: Fixed Fix Version/s: Impala 3.1.0 > TestSpillingNoDebugActionDimensions

[jira] [Resolved] (IMPALA-7697) Query gets erased before the client gets a chance to call get_log to fetch the error string

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7697. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Query gets erased before the client

[jira] [Updated] (IMPALA-7697) flakiness in test_resource_limits: query completes execution faster than expected

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7697: --- Summary: flakiness in test_resource_limits: query completes execution faster than expected

[jira] [Assigned] (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 ] Bikramjeet Vig reassigned IMPALA-7735: -- Assignee: Bikramjeet Vig (was: Tim Armstrong) > Expose admission control status in i

[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 ] Bikramjeet Vig updated IMPALA-7735: --- Attachment: Screenshot1.png > Expose admission control status in impala-shell >

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

[ https://issues.apache.org/jira/browse/IMPALA-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659891#comment-16659891 ] Bikramjeet Vig commented on IMPALA-7735: [~tarmstrong] do you think we should al

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

[ https://issues.apache.org/jira/browse/IMPALA-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661331#comment-16661331 ] Bikramjeet Vig commented on IMPALA-6352: [~tarmstrong] don't think so, haven't s

[jira] [Assigned] (IMPALA-7266) test_insert failure: Unable to drop partition on s3

[ https://issues.apache.org/jira/browse/IMPALA-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7266: -- Assignee: Bikramjeet Vig (was: Sailesh Mukil) > test_insert failure: Unable to drop

[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=16667577#comment-16667577 ] Bikramjeet Vig commented on IMPALA-2566: [~tarmstrong] Sure I'll take a look >

[jira] [Resolved] (IMPALA-7266) test_insert failure: Unable to drop partition on s3

[ https://issues.apache.org/jira/browse/IMPALA-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7266. Resolution: Information Provided The symptom looks similar to IMPALA-6094 which as [~saile

[jira] [Commented] (IMPALA-7244) Impala 3.1 Doc: Remove unsupported format write support

[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667925#comment-16667925 ] Bikramjeet Vig commented on IMPALA-7244: [~arodoni_cloudera] Looks like there ar

[jira] [Resolved] (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 ] Bikramjeet Vig resolved IMPALA-7735. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Expose admission control status in

[jira] [Commented] (IMPALA-7190) Remove unsupported format write support

[ https://issues.apache.org/jira/browse/IMPALA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669079#comment-16669079 ] Bikramjeet Vig commented on IMPALA-7190: I don't think this is a compatibility b

[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=16669156#comment-16669156 ] Bikramjeet Vig commented on IMPALA-2566: [~tarmstrong] seems like all cast funct

[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=16669195#comment-16669195 ] Bikramjeet Vig commented on IMPALA-2566: [~tarmstrong] Ah I just saw the note [

[jira] [Resolved] (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 ] Bikramjeet Vig resolved IMPALA-2566. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Result of casttochar() not handled

[jira] [Assigned] (IMPALA-7528) Division by zero when computing cardinalities of many to many joins on NULL columns

[ https://issues.apache.org/jira/browse/IMPALA-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7528: -- Assignee: Bikramjeet Vig (was: Adrian Ng) > Division by zero when computing cardinal

[jira] [Resolved] (IMPALA-7528) Division by zero when computing cardinalities of many to many joins on NULL columns

[ https://issues.apache.org/jira/browse/IMPALA-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7528. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Division by zero when computing car

[jira] [Commented] (IMPALA-6263) Assert hit during service restart Mutex.cpp:130: apache::thrift::concurrency::Mutex::impl::~impl(): Assertion `ret == 0' failed

[ https://issues.apache.org/jira/browse/IMPALA-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685606#comment-16685606 ] Bikramjeet Vig commented on IMPALA-6263: Happened recently during an exhaustive

[jira] [Comment Edited] (IMPALA-6263) Assert hit during service restart Mutex.cpp:130: apache::thrift::concurrency::Mutex::impl::~impl(): Assertion `ret == 0' failed

[ https://issues.apache.org/jira/browse/IMPALA-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685606#comment-16685606 ] Bikramjeet Vig edited comment on IMPALA-6263 at 11/13/18 7:00 PM:

[jira] [Created] (IMPALA-7851) TestFetchFirst::test_query_stmts_v6 hang during core asan build

Bikramjeet Vig created IMPALA-7851: -- Summary: TestFetchFirst::test_query_stmts_v6 hang during core asan build Key: IMPALA-7851 URL: https://issues.apache.org/jira/browse/IMPALA-7851 Project: IMPALA

[jira] [Created] (IMPALA-7852) test_hash_join_timer flakiness on s3 testing build

Bikramjeet Vig created IMPALA-7852: -- Summary: test_hash_join_timer flakiness on s3 testing build Key: IMPALA-7852 URL: https://issues.apache.org/jira/browse/IMPALA-7852 Project: IMPALA Issue

[jira] [Assigned] (IMPALA-7852) test_hash_join_timer flakiness on s3 testing build

[ https://issues.apache.org/jira/browse/IMPALA-7852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7852: -- Assignee: Michael Ho > test_hash_join_timer flakiness on s3 testing build > -

[jira] [Resolved] (IMPALA-7837) SCAN_BYTES_LIMIT="100M" test failing to raise exception in release build

[ https://issues.apache.org/jira/browse/IMPALA-7837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7837. Resolution: Fixed Fix Version/s: Impala 3.2.0 > SCAN_BYTES_LIMIT="100M" test failin

[jira] [Created] (IMPALA-7856) test_exchange_mem_usage_scaling failing, not hitting expected OOM

Bikramjeet Vig created IMPALA-7856: -- Summary: test_exchange_mem_usage_scaling failing, not hitting expected OOM Key: IMPALA-7856 URL: https://issues.apache.org/jira/browse/IMPALA-7856 Project: IMPALA

[jira] [Assigned] (IMPALA-7856) test_exchange_mem_usage_scaling failing, not hitting expected OOM

[ https://issues.apache.org/jira/browse/IMPALA-7856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7856: -- Assignee: Bikramjeet Vig > test_exchange_mem_usage_scaling failing, not hitting expec

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16710865#comment-16710865 ] Bikramjeet Vig commented on IMPALA-7351: Yes, I still have to look at sinks. Wil

[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: https://issues.apache.org/j

[jira] [Resolved] (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 ] Bikramjeet Vig resolved IMPALA-7960. Resolution: Fixed Fix Version/s: Impala 3.2.0 > wrong results when comparing timest

[jira] [Reopened] (IMPALA-5929) Remove useless explicit casts to string

[ https://issues.apache.org/jira/browse/IMPALA-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reopened IMPALA-5929: > Remove useless explicit casts to string > --- > >

[jira] [Resolved] (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 ] Bikramjeet Vig resolved IMPALA-7696. Resolution: Cannot Reproduce I am closing this based on the lack of relevant logging, Tim'

[jira] [Resolved] (IMPALA-3600) Add missing admission control test coverage

[ https://issues.apache.org/jira/browse/IMPALA-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-3600. Resolution: Fixed > Add missing admission control test coverage >

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16720673#comment-16720673 ] Bikramjeet Vig commented on IMPALA-7351: All of the missing estimates seem to be

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

[ https://issues.apache.org/jira/browse/IMPALA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7353. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Fix bogus too-high memory estimates

[jira] [Commented] (IMPALA-7994) Queries hitting memory limit issues in release builds

[ https://issues.apache.org/jira/browse/IMPALA-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724548#comment-16724548 ] Bikramjeet Vig commented on IMPALA-7994: IMPALA-7906 might be related, consideri

[jira] [Commented] (IMPALA-7994) Queries hitting memory limit issues in release builds

[ https://issues.apache.org/jira/browse/IMPALA-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724551#comment-16724551 ] Bikramjeet Vig commented on IMPALA-7994: IMPALA-7925, same thing here, this was

[jira] [Commented] (IMPALA-7994) Queries hitting memory limit issues in release builds

[ https://issues.apache.org/jira/browse/IMPALA-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724578#comment-16724578 ] Bikramjeet Vig commented on IMPALA-7994: Yup, thats what I am gonna do for now t

[jira] [Closed] (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 ] Bikramjeet Vig closed IMPALA-6352. -- Resolution: Cannot Reproduce > TestTableSample took too long in recent tests > ---

[jira] [Commented] (IMPALA-7994) Queries hitting memory limit issues in release builds

[ https://issues.apache.org/jira/browse/IMPALA-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726150#comment-16726150 ] Bikramjeet Vig commented on IMPALA-7994: Keeping this open for a while to make s

[jira] [Created] (IMPALA-8027) KRPC datastream timing out on both the receiver and sender side even in a minicluster

Bikramjeet Vig created IMPALA-8027: -- Summary: KRPC datastream timing out on both the receiver and sender side even in a minicluster Key: IMPALA-8027 URL: https://issues.apache.org/jira/browse/IMPALA-8027

[jira] [Resolved] (IMPALA-7925) test_bloom_filters and test_hdfs_scanner_profile running out of memory during exhaustive tests

[ https://issues.apache.org/jira/browse/IMPALA-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7925. Resolution: Fixed Fix Version/s: Impala 3.2.0 resolved the duplicate issue IMPALA-7

[jira] [Resolved] (IMPALA-7994) Queries hitting memory limit issues in release builds

[ https://issues.apache.org/jira/browse/IMPALA-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7994. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Queries hitting memory limit issues

[jira] [Commented] (IMPALA-6852) Add a section to the query profile covering number of fragments and total bytes scanned per host

[ https://issues.apache.org/jira/browse/IMPALA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740941#comment-16740941 ] Bikramjeet Vig commented on IMPALA-6852: [~tarmstrong] Do you think the number o

[jira] [Assigned] (IMPALA-6852) Add a section to the query profile covering number of fragments and total bytes scanned per host

[ https://issues.apache.org/jira/browse/IMPALA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-6852: -- Assignee: Alice Fan > Add a section to the query profile covering number of fragments

[jira] [Created] (IMPALA-8092) Add a debug page to provide better observability for admission control

Bikramjeet Vig created IMPALA-8092: -- Summary: Add a debug page to provide better observability for admission control Key: IMPALA-8092 URL: https://issues.apache.org/jira/browse/IMPALA-8092 Project: I

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16751586#comment-16751586 ] Bikramjeet Vig commented on IMPALA-7351: [~tarmstrong] Only PlanRootSink is left

[jira] [Updated] (IMPALA-6852) Add a section to the query profile covering number of fragments instances and total bytes scanned per host

[ https://issues.apache.org/jira/browse/IMPALA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-6852: --- Summary: Add a section to the query profile covering number of fragments instances and total

[jira] [Resolved] (IMPALA-8092) Add a debug page to provide better observability for admission control

[ https://issues.apache.org/jira/browse/IMPALA-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-8092. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Add a debug page to provide better

[jira] [Created] (IMPALA-8162) Add memory reserved and memory admitted per backend to the /backends debug page

Bikramjeet Vig created IMPALA-8162: -- Summary: Add memory reserved and memory admitted per backend to the /backends debug page Key: IMPALA-8162 URL: https://issues.apache.org/jira/browse/IMPALA-8162 P

[jira] [Resolved] (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:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7565. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Extends TAcceptQueueServer connecti

[jira] [Resolved] (IMPALA-8162) Add memory reserved and memory admitted per backend to the /backends debug page

[ https://issues.apache.org/jira/browse/IMPALA-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-8162. Resolution: Fixed Fix Version/s: Impala 3.2.0 > Add memory reserved and memory admi

[jira] [Commented] (IMPALA-7665) Bringing up stopped statestore causes queries to fail

[ https://issues.apache.org/jira/browse/IMPALA-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766372#comment-16766372 ] Bikramjeet Vig commented on IMPALA-7665: A possible solution: Use the same time

[jira] [Commented] (IMPALA-7665) Bringing up stopped statestore causes queries to fail

[ https://issues.apache.org/jira/browse/IMPALA-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766621#comment-16766621 ] Bikramjeet Vig commented on IMPALA-7665: [~tarmstrong] - I don't think we need t

[jira] [Commented] (IMPALA-7833) Audit and fix other string builtins for long string handling

[ https://issues.apache.org/jira/browse/IMPALA-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768814#comment-16768814 ] Bikramjeet Vig commented on IMPALA-7833: Additional Possible suspects: ConcatWs/

[jira] [Commented] (IMPALA-7833) Audit and fix other string builtins for long string handling

[ https://issues.apache.org/jira/browse/IMPALA-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768833#comment-16768833 ] Bikramjeet Vig commented on IMPALA-7833: Oh right, forgot about that query optio

[jira] [Commented] (IMPALA-8202) TestAdmissionControllerStress.test_mem_limit teardown() fails with "Invalid or unknown query handle"

[ https://issues.apache.org/jira/browse/IMPALA-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772493#comment-16772493 ] Bikramjeet Vig commented on IMPALA-8202: So far this is what i have found: every

[jira] [Commented] (IMPALA-6877) Allow setting -vmodule from debug page

[ https://issues.apache.org/jira/browse/IMPALA-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463013#comment-16463013 ] Bikramjeet Vig commented on IMPALA-6877: It turns out that using "-vmodule" dynam

[jira] [Commented] (IMPALA-5662) Log all information relevant to admission control decision making

[ https://issues.apache.org/jira/browse/IMPALA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463043#comment-16463043 ] Bikramjeet Vig commented on IMPALA-5662: [~tarmstrong] You are right that just lo

[jira] [Commented] (IMPALA-6877) Allow setting -vmodule from debug page

[ https://issues.apache.org/jira/browse/IMPALA-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463134#comment-16463134 ] Bikramjeet Vig commented on IMPALA-6877: [~bharathv]  All the vmodule patterns a

[jira] [Commented] (IMPALA-6865) session-expiry-test failed

[ https://issues.apache.org/jira/browse/IMPALA-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463205#comment-16463205 ] Bikramjeet Vig commented on IMPALA-6865: >From what I see, "TException: Could not

[jira] [Created] (IMPALA-7038) Update thread group name for threads created by client-request-state

Bikramjeet Vig created IMPALA-7038: -- Summary: Update thread group name for threads created by client-request-state Key: IMPALA-7038 URL: https://issues.apache.org/jira/browse/IMPALA-7038 Project: IMP

[jira] [Assigned] (IMPALA-7038) Update thread group name for threads created by client-request-state

[ https://issues.apache.org/jira/browse/IMPALA-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7038: -- Assignee: Bikramjeet Vig > Update thread group name for threads created by client-requ

[jira] [Resolved] (IMPALA-5662) Log all information relevant to admission control decision making

[ https://issues.apache.org/jira/browse/IMPALA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-5662. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Log all information relevant to admi

[jira] [Resolved] (IMPALA-3134) Admission controller should not assume all backends have same proc mem limit

[ https://issues.apache.org/jira/browse/IMPALA-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-3134. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Admission controller should not assu

[jira] [Closed] (IMPALA-6865) session-expiry-test failed

[ https://issues.apache.org/jira/browse/IMPALA-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig closed IMPALA-6865. -- Resolution: Not A Problem As mentioned in an earlier comment, this does not seem like a product

[jira] [Assigned] (IMPALA-7064) Local memory admitted metric does not get updated immediately

[ https://issues.apache.org/jira/browse/IMPALA-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7064: -- Assignee: Bikramjeet Vig > Local memory admitted metric does not get updated immediate

[jira] [Created] (IMPALA-7064) Local memory admitted metric does not get updated immediately

Bikramjeet Vig created IMPALA-7064: -- Summary: Local memory admitted metric does not get updated immediately Key: IMPALA-7064 URL: https://issues.apache.org/jira/browse/IMPALA-7064 Project: IMPALA

[jira] [Resolved] (IMPALA-6426) TestRuntimeRowFilters can fail due to differences in "Rows rejected"

[ https://issues.apache.org/jira/browse/IMPALA-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-6426. Resolution: Cannot Reproduce > TestRuntimeRowFilters can fail due to differences in "Rows r

[jira] [Created] (IMPALA-7081) Add test coverage for webserver calls

Bikramjeet Vig created IMPALA-7081: -- Summary: Add test coverage for webserver calls Key: IMPALA-7081 URL: https://issues.apache.org/jira/browse/IMPALA-7081 Project: IMPALA Issue Type: Improv

[jira] [Resolved] (IMPALA-6036) Queries in admission control pool queue stay in the queue even after end client had already disconnected.

[ https://issues.apache.org/jira/browse/IMPALA-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-6036. Resolution: Fixed Fix Version/s: Impala 3.1.0 Impala 2.13.0 > Qu

[jira] [Updated] (IMPALA-7064) Local memory admitted metric does not get updated immediately

[ https://issues.apache.org/jira/browse/IMPALA-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7064: --- Description: Due to a delay in updating (host_mem_reserved_[coord_id]) memory reserved loca

[jira] [Updated] (IMPALA-7190) Remove unsupported format write support

[ https://issues.apache.org/jira/browse/IMPALA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig updated IMPALA-7190: --- Description: Let's remove the formats gated by ALLOW_UNSUPPORTED_FORMATS since progress sta

[jira] [Commented] (IMPALA-6877) Allow setting -vmodule from debug page

[ https://issues.apache.org/jira/browse/IMPALA-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530400#comment-16530400 ] Bikramjeet Vig commented on IMPALA-6877: I am considering marking this as "Wont

[jira] [Resolved] (IMPALA-7190) Remove unsupported format write support

[ https://issues.apache.org/jira/browse/IMPALA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7190. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Remove unsupported format write sup

[jira] [Created] (IMPALA-7244) Doc: Remove unsupported format write support

Bikramjeet Vig created IMPALA-7244: -- Summary: Doc: Remove unsupported format write support Key: IMPALA-7244 URL: https://issues.apache.org/jira/browse/IMPALA-7244 Project: IMPALA Issue Type:

[jira] [Resolved] (IMPALA-6877) Allow setting -vmodule from debug page

[ https://issues.apache.org/jira/browse/IMPALA-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-6877. Resolution: Resolved > Allow setting -vmodule from debug page > --

[jira] [Assigned] (IMPALA-6299) IRBuilder codegen should using LLVMCodeGen::cpu_attrs instead of CpuInfo to determine valid instructions

[ https://issues.apache.org/jira/browse/IMPALA-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-6299: -- Assignee: Pooja Nilangekar > IRBuilder codegen should using LLVMCodeGen::cpu_attrs in

[jira] [Assigned] (IMPALA-6644) Add last heartbeat timestamp into Statestore metric

[ https://issues.apache.org/jira/browse/IMPALA-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-6644: -- Assignee: Pooja Nilangekar > Add last heartbeat timestamp into Statestore metric > --

[jira] [Created] (IMPALA-7266) test_insert failure: Unable to drop partition on s3

Bikramjeet Vig created IMPALA-7266: -- Summary: test_insert failure: Unable to drop partition on s3 Key: IMPALA-7266 URL: https://issues.apache.org/jira/browse/IMPALA-7266 Project: IMPALA Issu

[jira] [Assigned] (IMPALA-7266) test_insert failure: Unable to drop partition on s3

[ https://issues.apache.org/jira/browse/IMPALA-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7266: -- Assignee: Sailesh Mukil > test_insert failure: Unable to drop partition on s3 > -

[jira] [Created] (IMPALA-7279) test_rows_availability failing: incompatible regex

Bikramjeet Vig created IMPALA-7279: -- Summary: test_rows_availability failing: incompatible regex Key: IMPALA-7279 URL: https://issues.apache.org/jira/browse/IMPALA-7279 Project: IMPALA Issue

[jira] [Assigned] (IMPALA-7288) Codegen crash in FinalizeModule()

[ https://issues.apache.org/jira/browse/IMPALA-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig reassigned IMPALA-7288: -- Assignee: Bikramjeet Vig > Codegen crash in FinalizeModule() > --

[jira] [Work started] (IMPALA-7288) Codegen crash in FinalizeModule()

[ https://issues.apache.org/jira/browse/IMPALA-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7288 started by Bikramjeet Vig. -- > Codegen crash in FinalizeModule() > - > >

[jira] [Resolved] (IMPALA-7279) test_rows_availability failing: incompatible regex

[ https://issues.apache.org/jira/browse/IMPALA-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikramjeet Vig resolved IMPALA-7279. Resolution: Fixed Fix Version/s: Impala 3.1.0 > test_rows_availability failing: inc

  1   2   3   4   >