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

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

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

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

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

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

[jira] [Updated] (IMPALA-988) Join strategy (broadcast vs shuffle) decision does not take mem limit and other joins into account

[ https://issues.apache.org/jira/browse/IMPALA-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-988: - Issue Type: Improvement (was: Bug) > Join strategy (broadcast vs shuffle) decision does not

[jira] [Updated] (IMPALA-1023) Select nodes missing from plans result in minor inefficiencies.

[ https://issues.apache.org/jira/browse/IMPALA-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1023: -- Issue Type: Improvement (was: Bug) > Select nodes missing from plans result in minor

[jira] [Updated] (IMPALA-1076) Add a shell option to limit the maximum number of rows that are pretty printed

[ https://issues.apache.org/jira/browse/IMPALA-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1076: -- Issue Type: Improvement (was: Bug) > Add a shell option to limit the maximum number of rows

[jira] [Resolved] (IMPALA-2609) Table aliases with spaces do work properly

[ https://issues.apache.org/jira/browse/IMPALA-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2609. --- Resolution: Cannot Reproduce Assignee: (was: Syed A. Hashmi) > Table aliases with

[jira] [Resolved] (IMPALA-2692) Cancelling Timed Out Queries and/or Timed out connections

[ https://issues.apache.org/jira/browse/IMPALA-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2692. --- Resolution: Cannot Reproduce It's not clear what the problem actually is. Please reopen if

[jira] [Resolved] (IMPALA-3137) Switching between databases give a wrong result

[ https://issues.apache.org/jira/browse/IMPALA-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3137. --- Resolution: Invalid We don't track bugs with this driver on Apache JIRA. > Switching

[jira] [Updated] (IMPALA-3091) LLVM memory is not accounted for in query mem tracker

[ https://issues.apache.org/jira/browse/IMPALA-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3091: -- Issue Type: Improvement (was: Bug) > LLVM memory is not accounted for in query mem tracker >

[jira] [Created] (IMPALA-7785) Analyzer cannot handle GROUP BY clause rewrites

Paul Rogers created IMPALA-7785: --- Summary: Analyzer cannot handle GROUP BY clause rewrites Key: IMPALA-7785 URL: https://issues.apache.org/jira/browse/IMPALA-7785 Project: IMPALA Issue Type:

[jira] [Updated] (IMPALA-3636) Regression in DecimalOperators::EQ with codegen disabled

[ https://issues.apache.org/jira/browse/IMPALA-3636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3636: -- Issue Type: Improvement (was: Bug) > Regression in DecimalOperators::EQ with codegen

[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=16668898#comment-16668898 ] Sahil Takiar commented on IMPALA-7780: -- +1 to some type of long term solution to this. When

[jira] [Created] (IMPALA-7783) test_default_timezone failing on real cluster

David Knupp created IMPALA-7783: --- Summary: test_default_timezone failing on real cluster Key: IMPALA-7783 URL: https://issues.apache.org/jira/browse/IMPALA-7783 Project: IMPALA Issue Type: Bug

[jira] [Resolved] (IMPALA-2876) Investigate on applying rtm to spinlock

[ https://issues.apache.org/jira/browse/IMPALA-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2876. --- Resolution: Later > Investigate on applying rtm to spinlock >

[jira] [Updated] (IMPALA-3025) Add empty string test coverage

[ https://issues.apache.org/jira/browse/IMPALA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3025: -- Issue Type: Test (was: Bug) > Add empty string test coverage >

[jira] [Resolved] (IMPALA-2957) Query Profile: Incorrect "#Hosts" count in ExecSummary for SCAN NODE

[ https://issues.apache.org/jira/browse/IMPALA-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2957. --- Resolution: Duplicate > Query Profile: Incorrect "#Hosts" count in ExecSummary for SCAN

[jira] [Assigned] (IMPALA-3149) Bind variable issue in ODBC

[ https://issues.apache.org/jira/browse/IMPALA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-3149: - Assignee: (was: Syed A. Hashmi) > Bind variable issue in ODBC >

[jira] [Created] (IMPALA-7784) Partition pruning handles escaped strings incorrectly

Csaba Ringhofer created IMPALA-7784: --- Summary: Partition pruning handles escaped strings incorrectly Key: IMPALA-7784 URL: https://issues.apache.org/jira/browse/IMPALA-7784 Project: IMPALA

[jira] [Resolved] (IMPALA-3180) Impala Daemon Ready Status leading to Monitor-HostMonitor throttling_logger ERROR

[ https://issues.apache.org/jira/browse/IMPALA-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3180. --- Resolution: Invalid Looks like an issue with cloudera manager, which isn't an apache

[jira] [Resolved] (IMPALA-1159) fnv_hash UDF initialized with 32 bits offset basis

[ https://issues.apache.org/jira/browse/IMPALA-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-1159. --- Resolution: Won't Fix We've moved away from using FNV anyway, doesn't seem worth enhancing

[jira] [Updated] (IMPALA-1193) Restructure error handling within the impala-shell

[ https://issues.apache.org/jira/browse/IMPALA-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1193: -- Issue Type: Improvement (was: Bug) > Restructure error handling within the impala-shell >

[jira] [Updated] (IMPALA-6209) Impala - Allow override hadoop environmental variables for non-cdh installation

[ https://issues.apache.org/jira/browse/IMPALA-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6209: -- Issue Type: Improvement (was: Bug) > Impala - Allow override hadoop environmental variables

[jira] [Resolved] (IMPALA-3457) Cloudera Manager when adding HA Name Node does not properly update LOCATION column in table HIVE.SDS, nor DB_LOCATION_URI column in table HIVE.DBS causing all impala qu

[ https://issues.apache.org/jira/browse/IMPALA-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3457. --- Resolution: Invalid Cloudera manager is not an apache project, so we don't track issues

[jira] [Commented] (IMPALA-7733) TestInsertParquetQueries.test_insert_parquet is flaky in S3 due to rename

[ https://issues.apache.org/jira/browse/IMPALA-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668927#comment-16668927 ] Steve Loughran commented on IMPALA-7733: It could be your assertions are just brittle to change,

[jira] [Updated] (IMPALA-832) Negative look ahead using Regex does not work

[ https://issues.apache.org/jira/browse/IMPALA-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-832: - Issue Type: New Feature (was: Bug) > Negative look ahead using Regex does not work >

[jira] [Updated] (IMPALA-905) Admission control should enforce hierarchical pool limits

[ https://issues.apache.org/jira/browse/IMPALA-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-905: - Issue Type: New Feature (was: Bug) > Admission control should enforce hierarchical pool limits

[jira] [Updated] (IMPALA-2581) Push down "LIMIT" when possible

[ https://issues.apache.org/jira/browse/IMPALA-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2581: -- Issue Type: Improvement (was: Bug) > Push down "LIMIT" when possible >

[jira] [Updated] (IMPALA-2581) Push down LIMIT past DISTINCT

[ https://issues.apache.org/jira/browse/IMPALA-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Apple updated IMPALA-2581: -- Summary: Push down LIMIT past DISTINCT (was: Push down "LIMIT" when possible) > Push down LIMIT

[jira] [Updated] (IMPALA-2553) Impala should work correctly with Avro-based table containing Enum fields

[ https://issues.apache.org/jira/browse/IMPALA-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2553: -- Issue Type: New Feature (was: Bug) > Impala should work correctly with Avro-based table

[jira] [Resolved] (IMPALA-2626) In-flight queries fail when statestore comes back online.

[ https://issues.apache.org/jira/browse/IMPALA-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2626. --- Resolution: Duplicate > In-flight queries fail when statestore comes back online. >

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

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

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

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

[jira] [Updated] (IMPALA-1333) Missing implicit casts between char/varchar/string.

[ https://issues.apache.org/jira/browse/IMPALA-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1333: -- Issue Type: Improvement (was: Bug) > Missing implicit casts between char/varchar/string. >

[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=16669079#comment-16669079 ] Bikramjeet Vig commented on IMPALA-7190: I don't think this is a compatibility breaking release.

[jira] [Updated] (IMPALA-2398) [Nit]: Change error text on Explain Query for Compute Stats Command

[ https://issues.apache.org/jira/browse/IMPALA-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2398: -- Issue Type: Improvement (was: Bug) > [Nit]: Change error text on Explain Query for Compute

[jira] [Resolved] (IMPALA-2571) Flaky test: metadata.test_hdfs_permissions.TestHdfsPermissions.test_insert_into_read_only_table

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

[jira] [Updated] (IMPALA-2343) Capture operator timing information covering open/close & first/last batch close

[ https://issues.apache.org/jira/browse/IMPALA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2343: -- Issue Type: Improvement (was: Bug) > Capture operator timing information covering open/close

[jira] [Updated] (IMPALA-2746) Backend tests should pass with leak sanitizer enabled

[ https://issues.apache.org/jira/browse/IMPALA-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2746: -- Issue Type: Test (was: Bug) > Backend tests should pass with leak sanitizer enabled >

[jira] [Updated] (IMPALA-2729) Support default values for DECIMAL in Avro.

[ https://issues.apache.org/jira/browse/IMPALA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2729: -- Issue Type: New Feature (was: Bug) > Support default values for DECIMAL in Avro. >

[jira] [Updated] (IMPALA-2743) Propagate IS NOT NULL to scans from cols in inner joins

[ https://issues.apache.org/jira/browse/IMPALA-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2743: -- Issue Type: Improvement (was: Bug) > Propagate IS NOT NULL to scans from cols in inner joins

[jira] [Updated] (IMPALA-3181) build most of impala with -fno-exceptions

[ https://issues.apache.org/jira/browse/IMPALA-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3181: -- Issue Type: Improvement (was: Bug) > build most of impala with -fno-exceptions >

[jira] [Updated] (IMPALA-659) No Way to Escape Vertical Whitespace in Text Files

[ https://issues.apache.org/jira/browse/IMPALA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-659: - Issue Type: New Feature (was: Bug) > No Way to Escape Vertical Whitespace in Text Files >

[jira] [Updated] (IMPALA-3366) custom cluster tests should be more easily parallelizable

[ https://issues.apache.org/jira/browse/IMPALA-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3366: -- Issue Type: Improvement (was: Bug) > custom cluster tests should be more easily

[jira] [Updated] (IMPALA-3357) Sorter's quicksort implementation is very suboptimal for duplicate keys

[ https://issues.apache.org/jira/browse/IMPALA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3357: -- Issue Type: Improvement (was: Bug) > Sorter's quicksort implementation is very suboptimal

[jira] [Updated] (IMPALA-3366) custom cluster tests should be more easily parallelizable

[ https://issues.apache.org/jira/browse/IMPALA-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3366: -- Issue Type: Test (was: Improvement) > custom cluster tests should be more easily

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

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

[jira] [Updated] (IMPALA-1306) Avoid passing (empty) tuples of non-materialized slots, if consumer does not need them

[ https://issues.apache.org/jira/browse/IMPALA-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-1306: -- Issue Type: Improvement (was: Bug) > Avoid passing (empty) tuples of non-materialized slots,

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669101#comment-16669101 ] Paul Rogers edited comment on IMPALA-7655 at 10/30/18 5:36 PM: --- This fix

[jira] [Updated] (IMPALA-2850) Populate equivalence classes for <=>

[ https://issues.apache.org/jira/browse/IMPALA-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2850: -- Issue Type: Improvement (was: Bug) > Populate equivalence classes for <=> >

[jira] [Updated] (IMPALA-2783) Push down filters on rank similar to limit

[ https://issues.apache.org/jira/browse/IMPALA-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2783: -- Issue Type: Improvement (was: Bug) > Push down filters on rank similar to limit >

[jira] [Updated] (IMPALA-3109) For Avro table schema defined in tblproperties, add column should have no effect instead of writing to meta store

[ https://issues.apache.org/jira/browse/IMPALA-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3109: -- Issue Type: Improvement (was: Bug) > For Avro table schema defined in tblproperties, add

[jira] [Updated] (IMPALA-3171) data-source-tables.test is flaky when BATCH_SIZE is changed

[ https://issues.apache.org/jira/browse/IMPALA-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3171: -- Issue Type: Test (was: Bug) > data-source-tables.test is flaky when BATCH_SIZE is changed >

[jira] [Updated] (IMPALA-3171) data-source-tables.test is flaky when BATCH_SIZE is changed

[ https://issues.apache.org/jira/browse/IMPALA-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3171: -- Component/s: (was: Backend) Infrastructure > data-source-tables.test is

[jira] [Resolved] (IMPALA-1798) Very slow performance of Views on top of another Views

[ https://issues.apache.org/jira/browse/IMPALA-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-1798. --- Resolution: Duplicate Sounds like IMPALA-4242 > Very slow performance of Views on top of

[jira] [Commented] (IMPALA-7166) ExecSummary should be a first class object

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

[jira] [Assigned] (IMPALA-6777) Whitespace inconsistencies in pretty printer across units

[ https://issues.apache.org/jira/browse/IMPALA-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Sherman reassigned IMPALA-6777: -- Assignee: (was: Andrew Sherman) > Whitespace inconsistencies in pretty printer

[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] [Resolved] (IMPALA-3473) Flaky Test Failure: KuduTableSinkTest.TestInsertJustKey

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

[jira] [Updated] (IMPALA-6146) Rethink HdfsTextScanner::FillByteBuffer() extension point

[ https://issues.apache.org/jira/browse/IMPALA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6146: -- Issue Type: Improvement (was: Bug) > Rethink HdfsTextScanner::FillByteBuffer() extension

[jira] [Updated] (IMPALA-2543) Typo in timestamp value produces corrupt result instead of an error

[ https://issues.apache.org/jira/browse/IMPALA-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2543: -- Priority: Major (was: Minor) > Typo in timestamp value produces corrupt result instead of an

[jira] [Commented] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669101#comment-16669101 ] Paul Rogers commented on IMPALA-7655: - This fix runs into deeper problems: looks like {{CASE}} may

[jira] [Updated] (IMPALA-2543) Typo in timestamp value produces corrupt result instead of an error

[ https://issues.apache.org/jira/browse/IMPALA-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2543: -- Labels: correctness timestamp usability (was: timestamp usability) > Typo in timestamp value

[jira] [Resolved] (IMPALA-2629) CLONE - Impala Jdbc throws exception "[Simba][ImpalaJDBCDriver](500320) " where Impala Hue works fine

[ https://issues.apache.org/jira/browse/IMPALA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2629. --- Resolution: Invalid We don't track issues with these drivers here. > CLONE - Impala Jdbc

[jira] [Resolved] (IMPALA-2933) Impala-shell doesn't validate query options

[ https://issues.apache.org/jira/browse/IMPALA-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2933. --- Resolution: Won't Fix It's not clear that it's worth the shell doing an RPC per "set"

[jira] [Updated] (IMPALA-2939) Nested Types : Address Runtime & Scoped timer overhead

[ https://issues.apache.org/jira/browse/IMPALA-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2939: -- Issue Type: Improvement (was: Bug) > Nested Types : Address Runtime & Scoped timer overhead

[jira] [Updated] (IMPALA-7785) GROUP BY clause cannot contain a CASE statement

[ https://issues.apache.org/jira/browse/IMPALA-7785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7785: Summary: GROUP BY clause cannot contain a CASE statement (was: Analyzer cannot handle GROUP BY

[jira] [Resolved] (IMPALA-3170) Large literal exponents cause many seconds of delay

[ https://issues.apache.org/jira/browse/IMPALA-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-3170. --- Resolution: Fixed Fix Version/s: Impala 3.0 3.0 no longer supports JDK7, so this

[jira] [Updated] (IMPALA-7142) Ability to use expressions on range partitions

[ https://issues.apache.org/jira/browse/IMPALA-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7142: -- Issue Type: New Feature (was: Bug) > Ability to use expressions on range partitions >

[jira] [Resolved] (IMPALA-6397) IllegalStateException in planning of aggregation with float and decimal literal child expressions

[ https://issues.apache.org/jira/browse/IMPALA-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6397. --- Resolution: Fixed Fix Version/s: Impala 3.0 This was fixed when decimal_v2 became

[jira] [Commented] (IMPALA-7785) GROUP BY clause cannot contain a CASE statement

[ https://issues.apache.org/jira/browse/IMPALA-7785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669216#comment-16669216 ] Philip Zeyliger commented on IMPALA-7785: - Hi Paul! I tried this on a recent (two weeks old?)

[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] [Updated] (IMPALA-3073) Verify if compressed data in avro, sequence file format could be multistream

[ https://issues.apache.org/jira/browse/IMPALA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3073: -- Issue Type: New Feature (was: Bug) > Verify if compressed data in avro, sequence file format

[jira] [Updated] (IMPALA-7785) GROUP BY clause cannot contain a CASE statement

[ https://issues.apache.org/jira/browse/IMPALA-7785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7785: Description: The FE cannot handle a {{CASE}} statement in a {{GROUP BY}} clause. As a result,

[jira] [Created] (IMPALA-7787) python26-incompatibility-check failed because of docker 503 Service Unavailable

Tim Armstrong created IMPALA-7787: - Summary: python26-incompatibility-check failed because of docker 503 Service Unavailable Key: IMPALA-7787 URL: https://issues.apache.org/jira/browse/IMPALA-7787

[jira] [Resolved] (IMPALA-728) HBase: NULL values not taken into account depending on the columns in SELECT

[ https://issues.apache.org/jira/browse/IMPALA-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-728. -- Resolution: Duplicate > HBase: NULL values not taken into account depending on the columns in

[jira] [Updated] (IMPALA-6856) High memory estimates in Impala 2.11

[ https://issues.apache.org/jira/browse/IMPALA-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6856: -- Labels: resource-management (was: ) > High memory estimates in Impala 2.11 >

[jira] [Updated] (IMPALA-5928) Add test for IMPALA-5890 to test_data_errors

[ https://issues.apache.org/jira/browse/IMPALA-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5928: -- Issue Type: Test (was: Bug) > Add test for IMPALA-5890 to test_data_errors >

[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=16669190#comment-16669190 ] Tim Armstrong commented on IMPALA-2566: --- [~bikramjeet.vig] maybe. I think the question is whether

[jira] [Comment Edited] (IMPALA-7655) Codegen output for conditional functions (if,isnull, coalesce) is very suboptimal

[ https://issues.apache.org/jira/browse/IMPALA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669101#comment-16669101 ] Paul Rogers edited comment on IMPALA-7655 at 10/30/18 7:00 PM: --- This fix

[jira] [Work started] (IMPALA-7786) Start Hive and HMS in debug mode in the mini cluster

[ https://issues.apache.org/jira/browse/IMPALA-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7786 started by Fredy Wijaya. > Start Hive and HMS in debug mode in the mini cluster >

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

[jira] [Resolved] (IMPALA-6111) Impala HBase compatability

[ https://issues.apache.org/jira/browse/IMPALA-6111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6111. --- Resolution: Cannot Reproduce Impala on HBase 2.x seems to be working now. > Impala HBase

[jira] [Updated] (IMPALA-7270) Improve the decimal fuzz test

[ https://issues.apache.org/jira/browse/IMPALA-7270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7270: -- Issue Type: Test (was: Bug) > Improve the decimal fuzz test > -

[jira] [Updated] (IMPALA-4870) Extend Catalog metrics

[ https://issues.apache.org/jira/browse/IMPALA-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4870: -- Issue Type: Improvement (was: Bug) > Extend Catalog metrics > -- > >

[jira] [Updated] (IMPALA-6856) High memory estimates in Impala 2.11

[ https://issues.apache.org/jira/browse/IMPALA-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6856: -- Component/s: Frontend > High memory estimates in Impala 2.11 >

[jira] [Updated] (IMPALA-6344) Optimize decimal multiplication

[ https://issues.apache.org/jira/browse/IMPALA-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6344: -- Issue Type: Improvement (was: Bug) > Optimize decimal multiplication >

[jira] [Updated] (IMPALA-2370) Impala on YARN integration

[ https://issues.apache.org/jira/browse/IMPALA-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-2370: -- Issue Type: New Feature (was: Bug) > Impala on YARN integration > --

[jira] [Updated] (IMPALA-3994) Anticipate effect of cardinality estimation error when deciding between broadcast and repartitioning join

[ https://issues.apache.org/jira/browse/IMPALA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-3994: -- Issue Type: Improvement (was: Bug) > Anticipate effect of cardinality estimation error when

[jira] [Updated] (IMPALA-4422) Write scheduler unit tests to verify that data structures are correctly populated

[ https://issues.apache.org/jira/browse/IMPALA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4422: -- Issue Type: Test (was: Bug) > Write scheduler unit tests to verify that data structures are

[jira] [Updated] (IMPALA-4805) Avoid hash exchanges before analytic functions in more situations.

[ https://issues.apache.org/jira/browse/IMPALA-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4805: -- Issue Type: Improvement (was: Bug) > Avoid hash exchanges before analytic functions in more

[jira] [Updated] (IMPALA-4606) Support DDL for specifying that a UDF is non-deterministic

[ https://issues.apache.org/jira/browse/IMPALA-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4606: -- Issue Type: New Feature (was: Bug) > Support DDL for specifying that a UDF is

[jira] [Updated] (IMPALA-4683) Intelligently blacklist scratch disks with physical I/O errors

[ https://issues.apache.org/jira/browse/IMPALA-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4683: -- Issue Type: Improvement (was: Bug) > Intelligently blacklist scratch disks with physical I/O

[jira] [Resolved] (IMPALA-6276) incorrect projection of null column in hbase

[ https://issues.apache.org/jira/browse/IMPALA-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-6276. --- Resolution: Duplicate > incorrect projection of null column in hbase >

[jira] [Updated] (IMPALA-4065) Inline comparator calls into TopN::InsertBatch()

[ https://issues.apache.org/jira/browse/IMPALA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4065: -- Issue Type: Improvement (was: Bug) > Inline comparator calls into TopN::InsertBatch() >

[jira] [Updated] (IMPALA-7153) filesystem_client methods expect unusual paths

[ https://issues.apache.org/jira/browse/IMPALA-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7153: -- Issue Type: Improvement (was: Bug) > filesystem_client methods expect unusual paths >

[jira] [Updated] (IMPALA-283) select count(*) produces inconsistent results for hbase tables because of NULL projection

[ https://issues.apache.org/jira/browse/IMPALA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-283: - Summary: select count(*) produces inconsistent results for hbase tables because of NULL

[jira] [Commented] (IMPALA-7784) Partition pruning handles escaped strings incorrectly

[ https://issues.apache.org/jira/browse/IMPALA-7784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669226#comment-16669226 ] Tim Armstrong commented on IMPALA-7784: --- I suspect some of the uses of getStringValue() in the

  1   2   >