[jira] [Created] (IMPALA-8453) fs.defaultFS (file:///) is not supported

Lycan created IMPALA-8453: - Summary: fs.defaultFS (file:///) is not supported Key: IMPALA-8453 URL: https://issues.apache.org/jira/browse/IMPALA-8453 Project: IMPALA Issue Type: Improvement

[jira] [Resolved] (IMPALA-1856) MetadataOp.getTypeInfo() does not return all supported types

[ https://issues.apache.org/jira/browse/IMPALA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Rawat resolved IMPALA-1856. Resolution: Resolved Fix Version/s: Impala 3.3.0 > MetadataOp.getTypeInfo() does

[jira] [Commented] (IMPALA-1856) MetadataOp.getTypeInfo() does not return all supported types

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

[jira] [Commented] (IMPALA-8295) test_mem_limit in test_admission_controller timed out waiting for query to end

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

[jira] [Resolved] (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 ] Tim Armstrong resolved IMPALA-7814. --- Resolution: Incomplete I read this a couple of times and I don't understand exactly what

[jira] [Resolved] (IMPALA-7843) MT_DOP should be configurable per subquery

[ https://issues.apache.org/jira/browse/IMPALA-7843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7843. --- Resolution: Won't Do I don't think this is viable to implement. > MT_DOP should be

[jira] [Updated] (IMPALA-8013) Switch from boost:: to std:: locks

[ https://issues.apache.org/jira/browse/IMPALA-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8013: -- Description: We use boost::unique_lock, boost::lock_guard, boost::mutex, etc throughout the

[jira] [Resolved] (IMPALA-8057) Unhelpful messages in impalad.INFO log

[ https://issues.apache.org/jira/browse/IMPALA-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-8057. --- Resolution: Later I don't think it's worth tracking tasks of this granularity unless

[jira] [Updated] (IMPALA-8079) Introduce Parameter to control number of threads

[ https://issues.apache.org/jira/browse/IMPALA-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8079: -- Priority: Trivial (was: Major) > Introduce Parameter to control number of threads >

[jira] [Updated] (IMPALA-8110) Parquet stat filtering does not handle narrowed int types correctly

[ https://issues.apache.org/jira/browse/IMPALA-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8110: -- Priority: Critical (was: Major) > Parquet stat filtering does not handle narrowed int types

[jira] [Updated] (IMPALA-8230) Support trunc()/truncate() for DOUBLE type with decimal places argument

[ https://issues.apache.org/jira/browse/IMPALA-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8230: -- Priority: Minor (was: Major) > Support trunc()/truncate() for DOUBLE type with decimal

[jira] [Updated] (IMPALA-8230) Support trunc()/truncate() for DOUBLE type with decimal places argument

[ https://issues.apache.org/jira/browse/IMPALA-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8230: -- Summary: Support trunc()/truncate() for DOUBLE type with decimal places argument (was:

[jira] [Updated] (IMPALA-8230) Support trunc()/truncate() for DOUBLE type with decimal places argument

[ https://issues.apache.org/jira/browse/IMPALA-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8230: -- Issue Type: Improvement (was: Bug) > Support trunc()/truncate() for DOUBLE type with decimal

[jira] [Updated] (IMPALA-8230) Support trunc()/truncate() for DOUBLE type with decimal places argument

[ https://issues.apache.org/jira/browse/IMPALA-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8230: -- Component/s: Backend > Support trunc()/truncate() for DOUBLE type with decimal places

[jira] [Updated] (IMPALA-8230) ERROR: AnalysisException: No matching function with signature: trunc(DOUBLE, SMALLINT).

[ https://issues.apache.org/jira/browse/IMPALA-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8230: -- Description: trunc()/truncate() have one and two argument versions. The two argument version

[jira] [Assigned] (IMPALA-6590) Disable expr rewrites and codegen for VALUES() statements

[ https://issues.apache.org/jira/browse/IMPALA-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-6590: - Assignee: Abhishek Rawat > Disable expr rewrites and codegen for VALUES() statements >

[jira] [Updated] (IMPALA-8450) Add support for zstd and lz4 in parquet

[ https://issues.apache.org/jira/browse/IMPALA-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8450: -- Description: PARQUET-970 added these codecs to the format. We have LZ4 in the toolchain

[jira] [Commented] (IMPALA-8386) Incorrect predicate in a left outer join query

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

[jira] [Commented] (IMPALA-8420) Support HTTP based HS2/beeswax endpoints on coordinators

[ https://issues.apache.org/jira/browse/IMPALA-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825577#comment-16825577 ] bharath v commented on IMPALA-8420: --- [~arodoni_cloudera] Yes it will. Very likely we will introduce

[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=16825542#comment-16825542 ] Tim Armstrong commented on IMPALA-7665: --- I agree with that, this fixes the most severe of the

[jira] [Updated] (IMPALA-8174) test_catalog_restart failed with exception "Detected catalog service ID change"

[ https://issues.apache.org/jira/browse/IMPALA-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho updated IMPALA-8174: --- Affects Version/s: Impala 3.3.0 > test_catalog_restart failed with exception "Detected catalog

[jira] [Comment Edited] (IMPALA-8174) test_catalog_restart failed with exception "Detected catalog service ID change"

[ https://issues.apache.org/jira/browse/IMPALA-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825500#comment-16825500 ] Michael Ho edited comment on IMPALA-8174 at 4/24/19 9:01 PM: - Just happened

[jira] [Reopened] (IMPALA-8174) test_catalog_restart failed with exception "Detected catalog service ID change"

[ https://issues.apache.org/jira/browse/IMPALA-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Ho reopened IMPALA-8174: Just happened again. > test_catalog_restart failed with exception "Detected catalog service ID >

[jira] [Created] (IMPALA-8452) Avro scanner seems broken

Michael Ho created IMPALA-8452: -- Summary: Avro scanner seems broken Key: IMPALA-8452 URL: https://issues.apache.org/jira/browse/IMPALA-8452 Project: IMPALA Issue Type: Bug Components:

[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=16825496#comment-16825496 ] Bikramjeet Vig commented on IMPALA-7665: Statestore restart can cause transient failures for any

[jira] [Commented] (IMPALA-6691) KRPC w/ kerberos fails on SLES11

[ https://issues.apache.org/jira/browse/IMPALA-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825479#comment-16825479 ] Tim Armstrong commented on IMPALA-6691: --- We've seen a similar error message pop up occur when

[jira] [Updated] (IMPALA-8121) Pick better default flags in containers

[ https://issues.apache.org/jira/browse/IMPALA-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-8121: -- Description: There are some new features of Impala that are done but disabled by default

[jira] [Commented] (IMPALA-8121) Pick better default flags in containers

[ https://issues.apache.org/jira/browse/IMPALA-8121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825469#comment-16825469 ] Tim Armstrong commented on IMPALA-8121: --- IMPALA-5212 may make the pread issue moot if it's enabled

[jira] [Created] (IMPALA-8451) Default configs for admission control

Tim Armstrong created IMPALA-8451: - Summary: Default configs for admission control Key: IMPALA-8451 URL: https://issues.apache.org/jira/browse/IMPALA-8451 Project: IMPALA Issue Type:

[jira] [Created] (IMPALA-8450) Add support for zstd and lz4 in parquet

Tim Armstrong created IMPALA-8450: - Summary: Add support for zstd and lz4 in parquet Key: IMPALA-8450 URL: https://issues.apache.org/jira/browse/IMPALA-8450 Project: IMPALA Issue Type:

[jira] [Commented] (IMPALA-8444) Analysis perf regression after IMPALA-7616

[ https://issues.apache.org/jira/browse/IMPALA-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825394#comment-16825394 ] bharath v commented on IMPALA-8444: --- [~csringhofer] Nice catch. That should make it much faster. >

[jira] [Updated] (IMPALA-1856) MetadataOp.getTypeInfo() does not return all supported types

[ https://issues.apache.org/jira/browse/IMPALA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Rawat updated IMPALA-1856: --- Summary: MetadataOp.getTypeInfo() does not return all supported types (was: Missing

[jira] [Updated] (IMPALA-1856) Missing datatypes from JDBC DBMD.getTypeInfo() call

[ https://issues.apache.org/jira/browse/IMPALA-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Rawat updated IMPALA-1856: --- Description: The MetadataOp.getTypeInfo() does not return all the supported types. It's

[jira] [Updated] (IMPALA-8403) Possible thread leak in impalad

[ https://issues.apache.org/jira/browse/IMPALA-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quanlong Huang updated IMPALA-8403: --- Affects Version/s: Impala 2.12.0 > Possible thread leak in impalad >

[jira] [Commented] (IMPALA-8403) Possible thread leak in impalad

[ https://issues.apache.org/jira/browse/IMPALA-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824868#comment-16824868 ] Quanlong Huang commented on IMPALA-8403: I trigger a minidump and resove the threads. Most of