[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621472#comment-16621472 ] Philip Zeyliger commented on IMPALA-7310: - I've not looked at how that test is h

[jira] [Comment Edited] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621434#comment-16621434 ] Paul Rogers edited comment on IMPALA-7310 at 9/20/18 3:02 AM:

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621434#comment-16621434 ] Paul Rogers commented on IMPALA-7310: - Odd. Looked at the tests in {{ExprNdvTest}}.

[jira] [Comment Edited] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621096#comment-16621096 ] Paul Rogers edited comment on IMPALA-7310 at 9/20/18 1:50 AM:

[jira] [Resolved] (IMPALA-7422) Crash in QueryState::PublishFilter() fragment_map_.count(params.dst_fragment_idx) == 1 (0 vs. 1)

[ https://issues.apache.org/jira/browse/IMPALA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho resolved IMPALA-7422. Resolution: Fixed Fix Version/s: Impala 3.1.0 > Crash in QueryState::PublishFilter() > fra

[jira] [Commented] (IMPALA-7422) Crash in QueryState::PublishFilter() fragment_map_.count(params.dst_fragment_idx) == 1 (0 vs. 1)

[ https://issues.apache.org/jira/browse/IMPALA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621379#comment-16621379 ] Michael Ho commented on IMPALA-7422: [~tarmstrong], sorry for the late reply. Didn't

[jira] [Updated] (IMPALA-7597) "show partitions" does not retry on InconsistentMetadataFetchException

[ https://issues.apache.org/jira/browse/IMPALA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7597: -- Description: IMPALA-7530 added retries in case LocalCatalog throws InconsistentMetadataFetchException

[jira] [Updated] (IMPALA-7597) "show partitions" does not retry on InconsistentMetadataFetchException

[ https://issues.apache.org/jira/browse/IMPALA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7597: -- Description: IMPALA-7530 added retries in case LocalCatalog throws InconsistentMetadataFetchException

[jira] [Updated] (IMPALA-7599) Make num retries for InconsistentMetadataFetchException configurable

[ https://issues.apache.org/jira/browse/IMPALA-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7599: -- Issue Type: Improvement (was: Bug) > Make num retries for InconsistentMetadataFetchException configur

[jira] [Updated] (IMPALA-7599) Make num retries for InconsistentMetadataFetchException configurable

[ https://issues.apache.org/jira/browse/IMPALA-7599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bharath v updated IMPALA-7599: -- Summary: Make num retries for InconsistentMetadataFetchException configurable (was: Make the retries

[jira] [Commented] (IMPALA-7597) "show partitions" does not retry on InconsistentMetadataFetchException

[ https://issues.apache.org/jira/browse/IMPALA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621334#comment-16621334 ] bharath v commented on IMPALA-7597: --- Adrian, I raised a separate jira for it, IMPALA-7

[jira] [Created] (IMPALA-7599) Make the retries for InconsistentMetadataFetchException configurable

bharath v created IMPALA-7599: - Summary: Make the retries for InconsistentMetadataFetchException configurable Key: IMPALA-7599 URL: https://issues.apache.org/jira/browse/IMPALA-7599 Project: IMPALA

[jira] [Commented] (IMPALA-7597) "show partitions" does not retry on InconsistentMetadataFetchException

[ https://issues.apache.org/jira/browse/IMPALA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621330#comment-16621330 ] Adrian Ng commented on IMPALA-7597: --- As part of this fix, we should make #retries conf

[jira] [Created] (IMPALA-7598) Planner timeline not set in the runtime profile incase of errors

bharath v created IMPALA-7598: - Summary: Planner timeline not set in the runtime profile incase of errors Key: IMPALA-7598 URL: https://issues.apache.org/jira/browse/IMPALA-7598 Project: IMPALA

[jira] [Created] (IMPALA-7597) "show partitions" does not retry on InconsistentMetadataFetchException

bharath v created IMPALA-7597: - Summary: "show partitions" does not retry on InconsistentMetadataFetchException Key: IMPALA-7597 URL: https://issues.apache.org/jira/browse/IMPALA-7597 Project: IMPALA

[jira] [Resolved] (IMPALA-7420) Alternative cancellation messages with "internal" cancellation

[ https://issues.apache.org/jira/browse/IMPALA-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7420. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 I added the infra to do this and conver

[jira] [Commented] (IMPALA-7420) Alternative cancellation messages with "internal" cancellation

[ https://issues.apache.org/jira/browse/IMPALA-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621274#comment-16621274 ] ASF subversion and git services commented on IMPALA-7420: - Commi

[jira] [Commented] (IMPALA-7488) TestShellCommandLine::test_cancellation hangs occasionally

[ https://issues.apache.org/jira/browse/IMPALA-7488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621271#comment-16621271 ] ASF subversion and git services commented on IMPALA-7488: - Commi

[jira] [Commented] (IMPALA-6568) The profile of all statements should contain the Query Compilation timeline

[ https://issues.apache.org/jira/browse/IMPALA-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621273#comment-16621273 ] ASF subversion and git services commented on IMPALA-6568: - Commi

[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&focusedCommentId=16621275#comment-16621275 ] ASF subversion and git services commented on IMPALA-7418: - Commi

[jira] [Commented] (IMPALA-7579) TestObservability.test_query_profile_contains_all_events fails for S3 tests

[ https://issues.apache.org/jira/browse/IMPALA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621272#comment-16621272 ] ASF subversion and git services commented on IMPALA-7579: - Commi

[jira] [Created] (IMPALA-7596) Expose JvmPauseMonitor and GC Metrics to Impala's metrics infrastructure

Philip Zeyliger created IMPALA-7596: --- Summary: Expose JvmPauseMonitor and GC Metrics to Impala's metrics infrastructure Key: IMPALA-7596 URL: https://issues.apache.org/jira/browse/IMPALA-7596 Projec

[jira] [Created] (IMPALA-7595) Check failed: IsValidTime(time_) at timestamp-value.h:322

Tim Armstrong created IMPALA-7595: - Summary: Check failed: IsValidTime(time_) at timestamp-value.h:322 Key: IMPALA-7595 URL: https://issues.apache.org/jira/browse/IMPALA-7595 Project: IMPALA

[jira] [Updated] (IMPALA-7582) Generate junit style symptoms for issues during cluster startup (minicluster and impala)

[ https://issues.apache.org/jira/browse/IMPALA-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nithya updated IMPALA-7582: --- Summary: Generate junit style symptoms for issues during cluster startup (minicluster and impala) (was: Gen

[jira] [Updated] (IMPALA-7582) Generate symptoms for issues during cluster startup (minicluster and impala)

[ https://issues.apache.org/jira/browse/IMPALA-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nithya updated IMPALA-7582: --- Description: Generate symptoms for steps in cluster startup (see testdata/bin/run-all.sh) As a sub-task for

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621222#comment-16621222 ] Paul Rogers commented on IMPALA-7310: - [~jeszyb], agree completely. Here I'm digging

[jira] [Assigned] (IMPALA-7584) test_set fails when run against external cluster

[ https://issues.apache.org/jira/browse/IMPALA-7584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7584: - Assignee: David Knupp (was: Tim Armstrong) > test_set fails when run against external

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621196#comment-16621196 ] Paul Rogers commented on IMPALA-7310: - Here, it is worth pointing out the risk of an

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621171#comment-16621171 ] Paul Rogers commented on IMPALA-7310: - The original description pointed out the meth

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621143#comment-16621143 ] Balazs Jeszenszky commented on IMPALA-7310: --- [~Paul.Rogers] this one is about

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621126#comment-16621126 ] Paul Rogers commented on IMPALA-7310: - As noted above, the code uses -1 as an "undef

[jira] [Commented] (IMPALA-7498) impalad should wait for catalogd during start up

[ https://issues.apache.org/jira/browse/IMPALA-7498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621102#comment-16621102 ] bharath v commented on IMPALA-7498: --- Todd, I looked at the code and I don't think it w

[jira] [Commented] (IMPALA-7310) Compute Stats not computing NULLs as a distinct value causing wrong estimates

[ https://issues.apache.org/jira/browse/IMPALA-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621096#comment-16621096 ] Paul Rogers commented on IMPALA-7310: - Simplest case: a binary predicate. Current be

[jira] [Commented] (IMPALA-7560) Better selectivity estimate for != (not equals) binary predicate

[ https://issues.apache.org/jira/browse/IMPALA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620946#comment-16620946 ] Paul Rogers commented on IMPALA-7560: - The table in DRILL-5254 suggests how to use t

[jira] [Work started] (IMPALA-7306) Add regression test for IMPALA-7305

[ https://issues.apache.org/jira/browse/IMPALA-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7306 started by Tim Armstrong. - > Add regression test for IMPALA-7305 > --- >

[jira] [Updated] (IMPALA-7594) TestAutomaticCatalogInvalidation.test_local_catalog and test_v1_catalog still hitting timeout

[ https://issues.apache.org/jira/browse/IMPALA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7594: -- Description: Similar to IMPALA-7580, I hit this on a build of one of my patches when running

[jira] [Updated] (IMPALA-7594) TestAutomaticCatalogInvalidation.test_local_catalog and test_v1_catalog still hitting timeout

[ https://issues.apache.org/jira/browse/IMPALA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7594: -- Summary: TestAutomaticCatalogInvalidation.test_local_catalog and test_v1_catalog still hitting

[jira] [Updated] (IMPALA-7594) TestAutomaticCatalogInvalidation.test_local_catalog still hitting timeout

[ https://issues.apache.org/jira/browse/IMPALA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7594: -- Description: Similar to IMPALA-7580, I hit this on a build of one of my patches when running

[jira] [Updated] (IMPALA-7594) TestAutomaticCatalogInvalidation.test_local_catalog still hitting timeout

[ https://issues.apache.org/jira/browse/IMPALA-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7594: -- Description: Similar to IMPALA-7580, I hit this on a build of one of my patches. The branch h

[jira] [Created] (IMPALA-7594) TestAutomaticCatalogInvalidation.test_local_catalog still hitting timeout

Tim Armstrong created IMPALA-7594: - Summary: TestAutomaticCatalogInvalidation.test_local_catalog still hitting timeout Key: IMPALA-7594 URL: https://issues.apache.org/jira/browse/IMPALA-7594 Project:

[jira] [Created] (IMPALA-7593) test_automatic_invalidation failing in S3

Thomas Tauber-Marshall created IMPALA-7593: -- Summary: test_automatic_invalidation failing in S3 Key: IMPALA-7593 URL: https://issues.apache.org/jira/browse/IMPALA-7593 Project: IMPALA

[jira] [Commented] (IMPALA-7581) Hang in buffer-pool-test

[ https://issues.apache.org/jira/browse/IMPALA-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620813#comment-16620813 ] Tim Armstrong commented on IMPALA-7581: --- I just discovered that I had a buffer-poo

[jira] [Resolved] (IMPALA-7588) incorrect HS2 null handling introduced by IMPALA-7477

[ https://issues.apache.org/jira/browse/IMPALA-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7588. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > incorrect HS2 null handling introduce

[jira] [Commented] (IMPALA-7588) incorrect HS2 null handling introduced by IMPALA-7477

[ https://issues.apache.org/jira/browse/IMPALA-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620613#comment-16620613 ] Zoltán Borók-Nagy commented on IMPALA-7588: --- I pushed in the revert of IMPALA-

[jira] [Created] (IMPALA-7592) Planner should correctly estimate UnionNode host count

Balazs Jeszenszky created IMPALA-7592: - Summary: Planner should correctly estimate UnionNode host count Key: IMPALA-7592 URL: https://issues.apache.org/jira/browse/IMPALA-7592 Project: IMPALA

[jira] [Commented] (IMPALA-7477) Improve QueryResultSet interface to allow appending a batch of rows at a time

[ https://issues.apache.org/jira/browse/IMPALA-7477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620426#comment-16620426 ] ASF subversion and git services commented on IMPALA-7477: - Commi