[jira] [Assigned] (IMPALA-7653) Improve accuracy of compute incremental stats cardinality estimation

[ https://issues.apache.org/jira/browse/IMPALA-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7653: Assignee: Paul Rogers (was: Pooja Nilangekar) > Improve accuracy of compute

[jira] [Assigned] (IMPALA-7604) In AggregationNode.computeStats, handle cardinality overflow better

[ https://issues.apache.org/jira/browse/IMPALA-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7604: Assignee: Paul Rogers (was: Pooja Nilangekar) > In

[jira] [Assigned] (IMPALA-6544) Lack of S3 consistency leads to rare test failures

[ https://issues.apache.org/jira/browse/IMPALA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-6544: Assignee: Joe McDonnell (was: Pooja Nilangekar) > Lack of S3 consistency leads

[jira] [Resolved] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8189. -- Resolution: Fixed > TestParquet.test_resolution_by_name fails on S3 because 'hadoop

[jira] [Resolved] (IMPALA-5397) Set "End Time" earlier rather than on unregistration.

[ https://issues.apache.org/jira/browse/IMPALA-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-5397. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Set "End Time" earlier rather

[jira] [Resolved] (IMPALA-8245) Add hostname to timeout error message in HdfsMonitoredOps

[ https://issues.apache.org/jira/browse/IMPALA-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8245. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Add hostname to timeout error

[jira] [Assigned] (IMPALA-8245) Add hostname to timeout error message in HdfsMonitoredOps

[ https://issues.apache.org/jira/browse/IMPALA-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-8245: Assignee: Pooja Nilangekar > Add hostname to timeout error message in

[jira] [Resolved] (IMPALA-8064) test_min_max_filters is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8064. -- Resolution: Fixed > test_min_max_filters is flaky > -- >

[jira] [Commented] (IMPALA-8064) test_min_max_filters is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772500#comment-16772500 ] Pooja Nilangekar commented on IMPALA-8064: -- [~tarmstrong] I looked at a few other failed

[jira] [Commented] (IMPALA-8064) test_min_max_filters is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772342#comment-16772342 ] Pooja Nilangekar commented on IMPALA-8064: -- I had a look at the most recent failure. The

[jira] [Closed] (IMPALA-8201) How to generate erver-key.pem and server-cert.pem when executing the impala ssl test cases?

[ https://issues.apache.org/jira/browse/IMPALA-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar closed IMPALA-8201. Resolution: Information Provided > How to generate erver-key.pem and server-cert.pem when

[jira] [Commented] (IMPALA-8201) How to generate erver-key.pem and server-cert.pem when executing the impala ssl test cases?

[ https://issues.apache.org/jira/browse/IMPALA-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768755#comment-16768755 ] Pooja Nilangekar commented on IMPALA-8201: -- [~davidxdh] The instructions to generate the key

[jira] [Commented] (IMPALA-4268) Rework coordinator buffering to buffer more data

[ https://issues.apache.org/jira/browse/IMPALA-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766330#comment-16766330 ] Pooja Nilangekar commented on IMPALA-4268: -- Here is an update about the proposed solution:

[jira] [Commented] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16766289#comment-16766289 ] Pooja Nilangekar commented on IMPALA-8189: -- I'll take a look at this, it looks like this is due

[jira] [Assigned] (IMPALA-8189) TestParquet.test_resolution_by_name fails on S3 because 'hadoop fs -cp' fails

[ https://issues.apache.org/jira/browse/IMPALA-8189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-8189: Assignee: Pooja Nilangekar > TestParquet.test_resolution_by_name fails on S3

[jira] [Resolved] (IMPALA-8096) Limit on #rows returned from query

[ https://issues.apache.org/jira/browse/IMPALA-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8096. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Limit on #rows returned from

[jira] [Commented] (IMPALA-8064) test_min_max_filters is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762214#comment-16762214 ] Pooja Nilangekar commented on IMPALA-8064: -- Sure, taking a look at it right now. >

[jira] [Resolved] (IMPALA-8151) HiveUdfCall assumes StringValue is 16 bytes

[ https://issues.apache.org/jira/browse/IMPALA-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8151. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > HiveUdfCall assumes

[jira] [Commented] (IMPALA-8151) HiveUdfCall assumes StringValue is 16 bytes

[ https://issues.apache.org/jira/browse/IMPALA-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758629#comment-16758629 ] Pooja Nilangekar commented on IMPALA-8151: -- I agree. I believe it would make sense to use

[jira] [Resolved] (IMPALA-6932) Simple LIMIT 1 query can be really slow on many-filed sequence datasets

[ https://issues.apache.org/jira/browse/IMPALA-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-6932. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Simple LIMIT 1 query can be

[jira] [Resolved] (IMPALA-8064) test_min_max_filters is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8064. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > test_min_max_filters is flaky

[jira] [Assigned] (IMPALA-8096) Limit on #rows returned from query

[ https://issues.apache.org/jira/browse/IMPALA-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-8096: Assignee: Pooja Nilangekar > Limit on #rows returned from query >

[jira] [Resolved] (IMPALA-8007) test_slow_subscriber is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-8007. -- Resolution: Fixed > test_slow_subscriber is flaky > - > >

[jira] [Updated] (IMPALA-8064) test_min_max_filters is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-8064: - Description: The following configuration of the test_min_max_filters: {code:java}

[jira] [Created] (IMPALA-8064) test_min_max_filters is flaky

Pooja Nilangekar created IMPALA-8064: Summary: test_min_max_filters is flaky Key: IMPALA-8064 URL: https://issues.apache.org/jira/browse/IMPALA-8064 Project: IMPALA Issue Type: Bug

[jira] [Commented] (IMPALA-8063) Excessive logging from BeeswaxConnection::get_state() bloats JUnitXML output

[ https://issues.apache.org/jira/browse/IMPALA-8063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739018#comment-16739018 ] Pooja Nilangekar commented on IMPALA-8063: -- The sleep alone won't help since python's sleep

[jira] [Assigned] (IMPALA-6544) Lack of S3 consistency leads to rare test failures

[ https://issues.apache.org/jira/browse/IMPALA-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-6544: Assignee: Pooja Nilangekar > Lack of S3 consistency leads to rare test failures

[jira] [Created] (IMPALA-8059) TestWebPage::test_backend_states is flaky

Pooja Nilangekar created IMPALA-8059: Summary: TestWebPage::test_backend_states is flaky Key: IMPALA-8059 URL: https://issues.apache.org/jira/browse/IMPALA-8059 Project: IMPALA Issue

[jira] [Commented] (IMPALA-8007) test_slow_subscriber is flaky

[ https://issues.apache.org/jira/browse/IMPALA-8007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736730#comment-16736730 ] Pooja Nilangekar commented on IMPALA-8007: -- I was looking for reasons for the

[jira] [Resolved] (IMPALA-7882) ASAN failure in llvm-codegen-test

[ https://issues.apache.org/jira/browse/IMPALA-7882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7882. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > ASAN failure in

[jira] [Commented] (IMPALA-7878) Bad SQL generated by compute incremental stats

[ https://issues.apache.org/jira/browse/IMPALA-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695190#comment-16695190 ] Pooja Nilangekar commented on IMPALA-7878: -- [~Paul.Rogers] Assigning it to you because you've

[jira] [Resolved] (IMPALA-7873) TestExchangeMemUsage.test_exchange_mem_usage_scaling doesn't hit the memory limit

[ https://issues.apache.org/jira/browse/IMPALA-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7873. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 >

[jira] [Commented] (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:comment-tabpanel=16693727#comment-16693727 ] Pooja Nilangekar commented on IMPALA-7856: -- I guess this occurred before IMPALA-7367 went in.

[jira] [Commented] (IMPALA-7873) TestExchangeMemUsage.test_exchange_mem_usage_scaling doesn't hit the memory limit

[ https://issues.apache.org/jira/browse/IMPALA-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692521#comment-16692521 ] Pooja Nilangekar commented on IMPALA-7873: -- Yes, I hit the issue while testing IMPALA-7367. I

[jira] [Assigned] (IMPALA-7873) TestExchangeMemUsage.test_exchange_mem_usage_scaling doesn't hit the memory limit

[ https://issues.apache.org/jira/browse/IMPALA-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7873: Assignee: Pooja Nilangekar >

[jira] [Resolved] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7367. -- Resolution: Fixed Fix Version/s: Impala 3.2.0 > Pack StringValue,

[jira] [Resolved] (IMPALA-7791) Aggregation Node memory estimates don't account for number of fragment instances

[ https://issues.apache.org/jira/browse/IMPALA-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7791. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Aggregation Node memory

[jira] [Assigned] (IMPALA-7814) AggregationNode's memory estimate should be based on NDV only for non-grouping aggs

[ https://issues.apache.org/jira/browse/IMPALA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7814: Assignee: Pooja Nilangekar > AggregationNode's memory estimate should be based

[jira] [Updated] (IMPALA-7814) AggregationNode's memory estimate should be based on NDV only for non-grouping aggs

[ https://issues.apache.org/jira/browse/IMPALA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7814: - Description: Currently, the AggregationNode always computes the NDV to estimate the

[jira] [Updated] (IMPALA-7814) Aggregation Node's memory estimate should be based on NDV only for non-grouping aggs

[ https://issues.apache.org/jira/browse/IMPALA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7814: - Summary: Aggregation Node's memory estimate should be based on NDV only for

[jira] [Created] (IMPALA-7814) Aggregation Node

Pooja Nilangekar created IMPALA-7814: Summary: Aggregation Node Key: IMPALA-7814 URL: https://issues.apache.org/jira/browse/IMPALA-7814 Project: IMPALA Issue Type: Sub-task

[jira] [Updated] (IMPALA-7791) Aggregation Node memory estimates don't account for number of fragment instances

[ https://issues.apache.org/jira/browse/IMPALA-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7791: - Priority: Blocker (was: Major) > Aggregation Node memory estimates don't account for

[jira] [Resolved] (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 ] Pooja Nilangekar resolved IMPALA-7363. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Spurious error generated by

[jira] [Assigned] (IMPALA-7791) Aggregation Node memory estimates don't account for number of fragment instances

[ https://issues.apache.org/jira/browse/IMPALA-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7791: Assignee: Pooja Nilangekar > Aggregation Node memory estimates don't account for

[jira] [Updated] (IMPALA-7791) Aggregation Node memory estimates don't account for number of fragment instances

[ https://issues.apache.org/jira/browse/IMPALA-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7791: - Epic Color: ghx-label-7 (was: ghx-label-5) > Aggregation Node memory estimates don't

[jira] [Created] (IMPALA-7791) Aggregation Node memory estimates don't account for number of fragment instances

Pooja Nilangekar created IMPALA-7791: Summary: Aggregation Node memory estimates don't account for number of fragment instances Key: IMPALA-7791 URL: https://issues.apache.org/jira/browse/IMPALA-7791

[jira] [Comment Edited] (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:comment-tabpanel=16669233#comment-16669233 ] Pooja Nilangekar edited comment on IMPALA-7363 at 10/30/18 8:41 PM:

[jira] [Comment Edited] (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:comment-tabpanel=16669233#comment-16669233 ] Pooja Nilangekar edited comment on IMPALA-7363 at 10/30/18 8:41 PM:

[jira] [Commented] (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:comment-tabpanel=16669233#comment-16669233 ] Pooja Nilangekar commented on IMPALA-7363: -- This seems to be a non-deterministic bug, executing

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

[ https://issues.apache.org/jira/browse/IMPALA-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7749. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Merge aggregation node memory

[jira] [Commented] (IMPALA-7780) Rebase PlannerTest expected output for estimates, errors

[ https://issues.apache.org/jira/browse/IMPALA-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667720#comment-16667720 ] Pooja Nilangekar commented on IMPALA-7780: -- I have faced the issue of different estimates

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

[ https://issues.apache.org/jira/browse/IMPALA-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7749: Assignee: Pooja Nilangekar (was: Bikramjeet Vig) > Merge aggregation node

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

[ https://issues.apache.org/jira/browse/IMPALA-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7699: Assignee: Bikramjeet Vig (was: Tim Armstrong) >

[jira] [Created] (IMPALA-7700) test_shell_commandline.TestImpalaShell.test_cancellation failure

Pooja Nilangekar created IMPALA-7700: Summary: test_shell_commandline.TestImpalaShell.test_cancellation failure Key: IMPALA-7700 URL: https://issues.apache.org/jira/browse/IMPALA-7700 Project:

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

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7697: Assignee: Pooja Nilangekar > Query gets erased before reporting ExecSummary >

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

[ https://issues.apache.org/jira/browse/IMPALA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7697: Assignee: Bikramjeet Vig (was: Pooja Nilangekar) > Query gets erased before

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

Pooja Nilangekar created IMPALA-7699: Summary: TestSpillingNoDebugActionDimensions fails earlier than expected Key: IMPALA-7699 URL: https://issues.apache.org/jira/browse/IMPALA-7699 Project:

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

Pooja Nilangekar created IMPALA-7697: Summary: Query gets erased before reporting ExecSummary Key: IMPALA-7697 URL: https://issues.apache.org/jira/browse/IMPALA-7697 Project: IMPALA

[jira] [Created] (IMPALA-7678) Revert IMPALA-7660

Pooja Nilangekar created IMPALA-7678: Summary: Revert IMPALA-7660 Key: IMPALA-7678 URL: https://issues.apache.org/jira/browse/IMPALA-7678 Project: IMPALA Issue Type: Bug

[jira] [Commented] (IMPALA-7638) Lower default timeout for connection setup

[ https://issues.apache.org/jira/browse/IMPALA-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631201#comment-16631201 ] Pooja Nilangekar commented on IMPALA-7638: -- While reading the review for IMPALA-5394 to

[jira] [Resolved] (IMPALA-7352) HdfsTableSink doesn't take into account insert clustering

[ https://issues.apache.org/jira/browse/IMPALA-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7352. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > HdfsTableSink doesn't take

[jira] [Commented] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16626314#comment-16626314 ] Pooja Nilangekar commented on IMPALA-7367: -- >From what I understood, you're suggesting packing

[jira] [Assigned] (IMPALA-7352) HdfsTableSink doesn't take into account insert clustering

[ https://issues.apache.org/jira/browse/IMPALA-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7352: Assignee: Pooja Nilangekar (was: Bikramjeet Vig) > HdfsTableSink doesn't take

[jira] [Commented] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624368#comment-16624368 ] Pooja Nilangekar commented on IMPALA-7367: -- [~tarmstrong] I still need to fix issues with

[jira] [Assigned] (IMPALA-7545) Add admission control status to query log

[ https://issues.apache.org/jira/browse/IMPALA-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar reassigned IMPALA-7545: Assignee: Pooja Nilangekar (was: Tim Armstrong) > Add admission control status

[jira] [Resolved] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7335. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Assertion Failure -

[jira] [Resolved] (IMPALA-7430) Remove the log added to HdfsScanNode::ScannerThread

[ https://issues.apache.org/jira/browse/IMPALA-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7430. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Remove the log added to

[jira] [Comment Edited] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622879#comment-16622879 ] Pooja Nilangekar edited comment on IMPALA-7367 at 9/20/18 11:49 PM:

[jira] [Commented] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622879#comment-16622879 ] Pooja Nilangekar commented on IMPALA-7367: -- I ran TPCH with a scale factor of 60 on a

[jira] [Updated] (IMPALA-7430) Remove the log added to HdfsScanNode::ScannerThread

[ https://issues.apache.org/jira/browse/IMPALA-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7430: - Affects Version/s: Impala 3.1.0 > Remove the log added to HdfsScanNode::ScannerThread >

[jira] [Commented] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614152#comment-16614152 ] Pooja Nilangekar commented on IMPALA-7367: -- [~csringhofer] Agreed. We should be moving away

[jira] [Created] (IMPALA-7551) Inaccurate timeline for "Row Available"

Pooja Nilangekar created IMPALA-7551: Summary: Inaccurate timeline for "Row Available" Key: IMPALA-7551 URL: https://issues.apache.org/jira/browse/IMPALA-7551 Project: IMPALA Issue

[jira] [Commented] (IMPALA-4356) Automatically codegen expressions with any root Expr node

[ https://issues.apache.org/jira/browse/IMPALA-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604922#comment-16604922 ] Pooja Nilangekar commented on IMPALA-4356: -- There is a

[jira] [Comment Edited] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603589#comment-16603589 ] Pooja Nilangekar edited comment on IMPALA-7367 at 9/4/18 9:25 PM: --

[jira] [Commented] (IMPALA-7367) Pack StringValue, CollectionValue and TimestampValue slots

[ https://issues.apache.org/jira/browse/IMPALA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603589#comment-16603589 ] Pooja Nilangekar commented on IMPALA-7367: -- There is an issue with packing TimestampValue. GCC

[jira] [Resolved] (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 ] Pooja Nilangekar resolved IMPALA-6644. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Add last heartbeat timestamp

[jira] [Resolved] (IMPALA-7418) test_udf_errors - returns Cancelled instead of actual error

[ https://issues.apache.org/jira/browse/IMPALA-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7418. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > test_udf_errors - returns

[jira] [Commented] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590744#comment-16590744 ] Pooja Nilangekar commented on IMPALA-7335: -- I have not been able to reproduce this locally. I

[jira] [Comment Edited] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589578#comment-16589578 ] Pooja Nilangekar edited comment on IMPALA-7335 at 8/23/18 6:14 PM: ---

[jira] [Commented] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589578#comment-16589578 ] Pooja Nilangekar commented on IMPALA-7335: -- >From my understanding of the HdfsScanNode, here

[jira] [Comment Edited] (IMPALA-7418) test_udf_errors - returns Cancelled instead of actual error

[ https://issues.apache.org/jira/browse/IMPALA-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587876#comment-16587876 ] Pooja Nilangekar edited comment on IMPALA-7418 at 8/22/18 12:32 AM:

[jira] [Comment Edited] (IMPALA-7418) test_udf_errors - returns Cancelled instead of actual error

[ https://issues.apache.org/jira/browse/IMPALA-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587876#comment-16587876 ] Pooja Nilangekar edited comment on IMPALA-7418 at 8/22/18 12:32 AM:

[jira] [Commented] (IMPALA-7418) test_udf_errors - returns Cancelled instead of actual error

[ https://issues.apache.org/jira/browse/IMPALA-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16587876#comment-16587876 ] Pooja Nilangekar commented on IMPALA-7418: -- Looking at the latest repro of this issues, I think

[jira] [Comment Edited] (IMPALA-6932) Simple LIMIT 1 query can be really slow on many-filed sequence datasets

[ https://issues.apache.org/jira/browse/IMPALA-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586383#comment-16586383 ] Pooja Nilangekar edited comment on IMPALA-6932 at 8/20/18 7:14 PM: ---

[jira] [Commented] (IMPALA-6932) Simple LIMIT 1 query can be really slow on many-filed sequence datasets

[ https://issues.apache.org/jira/browse/IMPALA-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586383#comment-16586383 ] Pooja Nilangekar commented on IMPALA-6932: -- This issue is not specific to the Avro scanner. It

[jira] [Updated] (IMPALA-6932) Simple LIMIT 1 query can be really slow on many-filed sequence datasets

[ https://issues.apache.org/jira/browse/IMPALA-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-6932: - Summary: Simple LIMIT 1 query can be really slow on many-filed sequence datasets (was:

[jira] [Commented] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16582889#comment-16582889 ] Pooja Nilangekar commented on IMPALA-7335: -- Here is the log corresponding to the query failure:

[jira] [Updated] (IMPALA-7430) Remove the log added to HdfsScanNode::ScannerThread

[ https://issues.apache.org/jira/browse/IMPALA-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7430: - Description: Logs were added to the HdfsScanNode in order to debug IMPALA-7335 and

[jira] [Created] (IMPALA-7430) Remove the log added to HdfsScanNode::ScannerThread

Pooja Nilangekar created IMPALA-7430: Summary: Remove the log added to HdfsScanNode::ScannerThread Key: IMPALA-7430 URL: https://issues.apache.org/jira/browse/IMPALA-7430 Project: IMPALA

[jira] [Closed] (IMPALA-6153) Prevent Coordinator::UpdateFilter() running after query exec resources are released

[ https://issues.apache.org/jira/browse/IMPALA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar closed IMPALA-6153. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Prevent

[jira] [Commented] (IMPALA-7378) test_strict_mode failed on an ASAN build: expected "Error converting column: 5 to DOUBLE"

[ https://issues.apache.org/jira/browse/IMPALA-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568753#comment-16568753 ] Pooja Nilangekar commented on IMPALA-7378: -- I don't think this is specific to ASAN. [Example: 

[jira] [Resolved] (IMPALA-7234) Non-deterministic majority format for a table with equal partition instances

[ https://issues.apache.org/jira/browse/IMPALA-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7234. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > Non-deterministic majority

[jira] [Commented] (IMPALA-7378) test_strict_mode failed on an ASAN build: expected "Error converting column: 5 to DOUBLE"

[ https://issues.apache.org/jira/browse/IMPALA-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565643#comment-16565643 ] Pooja Nilangekar commented on IMPALA-7378: -- What you're saying makes sense but this query does

[jira] [Commented] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564560#comment-16564560 ] Pooja Nilangekar commented on IMPALA-7335: -- I think it is closer to IMPALA-7378. In this case,

[jira] [Commented] (IMPALA-7378) test_strict_mode failed on an ASAN build: expected "Error converting column: 5 to DOUBLE"

[ https://issues.apache.org/jira/browse/IMPALA-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564495#comment-16564495 ] Pooja Nilangekar commented on IMPALA-7378: -- [~tarmstrong] This seems weirder. In case of

[jira] [Commented] (IMPALA-7378) test_strict_mode failed on an ASAN build: expected "Error converting column: 5 to DOUBLE"

[ https://issues.apache.org/jira/browse/IMPALA-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564459#comment-16564459 ] Pooja Nilangekar commented on IMPALA-7378: -- Yes, it looks like the failures in the fragments

[jira] [Comment Edited] (IMPALA-7335) Assertion Failure - test_corrupt_files

[ https://issues.apache.org/jira/browse/IMPALA-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562750#comment-16562750 ] Pooja Nilangekar edited comment on IMPALA-7335 at 7/31/18 6:53 PM: ---

[jira] [Commented] (IMPALA-7209) Disallow self referencing ALTER VIEW statments

[ https://issues.apache.org/jira/browse/IMPALA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16564039#comment-16564039 ] Pooja Nilangekar commented on IMPALA-7209: -- [~tarmstrong] Done. > Disallow self referencing

[jira] [Updated] (IMPALA-7209) Disallow self referencing ALTER VIEW statments

[ https://issues.apache.org/jira/browse/IMPALA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar updated IMPALA-7209: - Fix Version/s: Impala 3.1.0 > Disallow self referencing ALTER VIEW statments >

[jira] [Resolved] (IMPALA-7209) Disallow self referencing ALTER VIEW statments

[ https://issues.apache.org/jira/browse/IMPALA-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pooja Nilangekar resolved IMPALA-7209. -- Resolution: Fixed > Disallow self referencing ALTER VIEW statments >

  1   2   >