[jira] [Updated] (IMPALA-7070) Failed test: query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays on S3

[ https://issues.apache.org/jira/browse/IMPALA-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7070: -- Target Version: Impala 3.1.0 > Failed test: >

[jira] [Commented] (IMPALA-7742) User names in Sentry are now case sensitive

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

[jira] [Commented] (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:comment-tabpanel=16667753#comment-16667753 ] ASF subversion and git services commented on IMPALA-7749: - Commit

[jira] [Updated] (IMPALA-7282) Sentry privilege disappears after a catalog refresh

[ https://issues.apache.org/jira/browse/IMPALA-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7282: -- Target Version: Impala 3.2.0 > Sentry privilege disappears after a catalog refresh >

[jira] [Updated] (IMPALA-6294) Concurrent hung with lots of spilling make slow progress due to blocking in DataStreamRecvr and DataStreamSender

[ https://issues.apache.org/jira/browse/IMPALA-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6294: -- Target Version: Impala 3.2.0 > Concurrent hung with lots of spilling make slow progress due

[jira] [Updated] (IMPALA-7183) We should print the sender name when logging a report for an unknown status report on the coordinatior

[ https://issues.apache.org/jira/browse/IMPALA-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7183: -- Target Version: Impala 3.2.0 > We should print the sender name when logging a report for an

[jira] [Updated] (IMPALA-7670) Drop table with a concurrent refresh throws ConcurrentModificationException

[ https://issues.apache.org/jira/browse/IMPALA-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7670: -- Target Version: Impala 3.2.0 > Drop table with a concurrent refresh throws

[jira] [Assigned] (IMPALA-7753) Rewrite engine ignores top-level expressions in ORDER BY clause

[ https://issues.apache.org/jira/browse/IMPALA-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned IMPALA-7753: --- Assignee: (was: Paul Rogers) Description: The select statement represents the

[jira] [Updated] (IMPALA-7750) Prune trivial ELSE clause in CASE simplification

[ https://issues.apache.org/jira/browse/IMPALA-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7750: Priority: Trivial (was: Major) Description: A trivial optimization is to omit ELSE if it

[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] [Updated] (IMPALA-6890) split-hbase.sh: Can't get master address from ZooKeeper; znode data == null

[ https://issues.apache.org/jira/browse/IMPALA-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6890: -- Target Version: Impala 3.1.0, Impala 2.13.0 (was: Impala 2.13.0) > split-hbase.sh: Can't get

[jira] [Assigned] (IMPALA-7755) IS [NOT] DISTINCT FROM rewrite rules don't handle aggregates

[ https://issues.apache.org/jira/browse/IMPALA-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned IMPALA-7755: --- Assignee: (was: Paul Rogers) Description: Testing revealed one issue and one

[jira] [Resolved] (IMPALA-7662) test_parquet reads bad_magic_number.parquet without an error

[ https://issues.apache.org/jira/browse/IMPALA-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-7662. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 > test_parquet reads

[jira] [Updated] (IMPALA-6048) Queries make very slow progress and report WaitForRPC() stuck for too long

[ https://issues.apache.org/jira/browse/IMPALA-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6048: -- Target Version: Impala 3.2.0 > Queries make very slow progress and report WaitForRPC() stuck

[jira] [Commented] (IMPALA-7565) Extends TAcceptQueueServer connection_setup_pool to be multi-threaded

[ https://issues.apache.org/jira/browse/IMPALA-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667597#comment-16667597 ] Michael Ho commented on IMPALA-7565: A minor first step is to convert {{CONNECTION_SETUP_POOL_SIZE}}

[jira] [Assigned] (IMPALA-7752) Stmt.reset() doesn't (and can't)

[ https://issues.apache.org/jira/browse/IMPALA-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned IMPALA-7752: --- Assignee: (was: Paul Rogers) Summary: Stmt.reset() doesn't (and can't) (was:

[jira] [Updated] (IMPALA-7523) Planner Test failing with "Failed to assign regions to servers after 60000 millis."

[ https://issues.apache.org/jira/browse/IMPALA-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7523: -- Target Version: Impala 3.2.0 > Planner Test failing with "Failed to assign regions to servers

[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=16667650#comment-16667650 ] Steve Loughran commented on IMPALA-7733: This looks like you are hitting S3 inconsistency;

[jira] [Commented] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667679#comment-16667679 ] Sahil Takiar commented on IMPALA-: -- An example query is: {code:java} select int_col from

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

Paul Rogers created IMPALA-7780: --- Summary: Rebase PlannerTest expected output for estimates, errors Key: IMPALA-7780 URL: https://issues.apache.org/jira/browse/IMPALA-7780 Project: IMPALA

[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=16667703#comment-16667703 ] Vuk Ercegovac commented on IMPALA-7733: --- Thanks for the background, so yes, agreed that this can't

[jira] [Updated] (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:all-tabpanel ] Vuk Ercegovac updated IMPALA-7733: -- Labels: (was: flaky-test) > TestInsertParquetQueries.test_insert_parquet is flaky in S3 due

[jira] [Resolved] (IMPALA-2680) Align un-aligned memory copies

[ https://issues.apache.org/jira/browse/IMPALA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-2680. --- Resolution: Won't Fix I don't think this actually makes sense, we've generally see that

[jira] [Created] (IMPALA-7781) Clean up ad-hoc instance of, casts to use predicates in expr rewriter

Paul Rogers created IMPALA-7781: --- Summary: Clean up ad-hoc instance of, casts to use predicates in expr rewriter Key: IMPALA-7781 URL: https://issues.apache.org/jira/browse/IMPALA-7781 Project: IMPALA

[jira] [Updated] (IMPALA-7070) Failed test: query_test.test_nested_types.TestParquetArrayEncodings.test_thrift_array_of_arrays on S3

[ https://issues.apache.org/jira/browse/IMPALA-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7070: -- Fix Version/s: (was: Impala 3.1.0) > Failed test: >

[jira] [Updated] (IMPALA-6890) split-hbase.sh: Can't get master address from ZooKeeper; znode data == null

[ https://issues.apache.org/jira/browse/IMPALA-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6890: -- Priority: Critical (was: Blocker) > split-hbase.sh: Can't get master address from ZooKeeper;

[jira] [Updated] (IMPALA-7003) Support erasure-coding in impala

[ https://issues.apache.org/jira/browse/IMPALA-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7003: -- Target Version: Product Backlog (was: Impala 3.2.0) I'll just put this on backlog until

[jira] [Comment Edited] (IMPALA-7565) Extends TAcceptQueueServer connection_setup_pool to be multi-threaded

[ https://issues.apache.org/jira/browse/IMPALA-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667597#comment-16667597 ] Michael Ho edited comment on IMPALA-7565 at 10/29/18 6:56 PM: -- A minor

[jira] [Updated] (IMPALA-6194) Ensure all fragment instances notice cancellation

[ https://issues.apache.org/jira/browse/IMPALA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6194: -- Target Version: Impala 3.2.0 > Ensure all fragment instances notice cancellation >

[jira] [Resolved] (IMPALA-7742) User names in Sentry are now case sensitive

[ https://issues.apache.org/jira/browse/IMPALA-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya resolved IMPALA-7742. -- Resolution: Fixed Fix Version/s: Impala 3.1.0 > User names in Sentry are now case

[jira] [Commented] (IMPALA-7741) Functions nvl2(), decode(), nullif() not listed in _impala_builtins

[ https://issues.apache.org/jira/browse/IMPALA-7741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667658#comment-16667658 ] Paul Rogers commented on IMPALA-7741: - We can solve the n^2 arguments problem by providing a custom

[jira] [Updated] (IMPALA-6692) When partition exchange is followed by sort each sort node becomes a synchronization point across the cluster

[ https://issues.apache.org/jira/browse/IMPALA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6692: -- Target Version: Impala 3.2.0 > When partition exchange is followed by sort each sort node

[jira] [Updated] (IMPALA-6808) Impala python code should be installed into infra/python/env like other packages

[ https://issues.apache.org/jira/browse/IMPALA-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6808: -- Target Version: Product Backlog Priority: Major (was: Critical) I'm just going to

[jira] [Updated] (IMPALA-6783) Rethink the end-to-end queuing at KrpcDataStreamReceiver

[ https://issues.apache.org/jira/browse/IMPALA-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6783: -- Target Version: Impala 3.2.0 > Rethink the end-to-end queuing at KrpcDataStreamReceiver >

[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] [Assigned] (IMPALA-7244) Impala 3.1 Doc: Remove unsupported format write support

[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni reassigned IMPALA-7244: --- Assignee: Alex Rodoni (was: Bikramjeet Vig) > Impala 3.1 Doc: Remove unsupported format

[jira] [Work started] (IMPALA-7687) Impala 3.1 Doc: Add support for multiple distinct operators in the same query block

[ https://issues.apache.org/jira/browse/IMPALA-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7687 started by Alex Rodoni. --- > Impala 3.1 Doc: Add support for multiple distinct operators in the same query

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

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

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

[ https://issues.apache.org/jira/browse/IMPALA-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7244 started by Alex Rodoni. --- > Impala 3.1 Doc: Remove unsupported format write support >

[jira] [Assigned] (IMPALA-7727) failed compute stats child query status no longer propagates to parent query

[ https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-7727: - Assignee: bharath v (was: Tim Armstrong) > failed compute stats child query status no

[jira] [Updated] (IMPALA-7102) Add a query option to enable/disable running queries erasure coded files

[ https://issues.apache.org/jira/browse/IMPALA-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7102: Labels: (was: future_release_doc) > Add a query option to enable/disable running queries

[jira] [Updated] (IMPALA-7687) Impala 3.1 Doc: Add support for multiple distinct operators in the same query block

[ https://issues.apache.org/jira/browse/IMPALA-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rodoni updated IMPALA-7687: Description: https://gerrit.cloudera.org/#/c/11823/ > Impala 3.1 Doc: Add support for multiple

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

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

[jira] [Updated] (IMPALA-7720) Allow longer timeout on expr-test

[ https://issues.apache.org/jira/browse/IMPALA-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Apple updated IMPALA-7720: -- Issue Type: Task (was: Sub-task) Parent: (was: IMPALA-5031) > Allow longer timeout on

[jira] [Commented] (IMPALA-7720) Allow longer timeout on expr-test

[ https://issues.apache.org/jira/browse/IMPALA-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667054#comment-16667054 ] Jim Apple commented on IMPALA-7720: --- This is now configurable in {{UBSAN_FULL}} at compile time. Since

[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=16667947#comment-16667947 ] Alex Rodoni commented on IMPALA-7190: - [~bikramjeet.vig] Most of the removed query options are being

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

[ https://issues.apache.org/jira/browse/IMPALA-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang resolved IMPALA-7166. --- Resolution: Fixed Fix Version/s: Impala 3.1.0 Many thanks to [~tarmstrong] for

[jira] [Commented] (IMPALA-7776) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667404#comment-16667404 ] Lars Volker commented on IMPALA-7776: - Duplicate of IMPALA-? > Fail queries where the sum of

[jira] [Updated] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-: - Component/s: Frontend > Fail queries where the sum of offset and limit exceed the max value of

[jira] [Resolved] (IMPALA-7758) chars_formats dependent tables are created using the wrong LOCATION

[ https://issues.apache.org/jira/browse/IMPALA-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Knupp resolved IMPALA-7758. - Resolution: Fixed Fix Version/s: Impala 3.1.0 > chars_formats dependent tables are

[jira] [Created] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

Sahil Takiar created IMPALA-: Summary: Fail queries where the sum of offset and limit exceed the max value of int64 Key: IMPALA- URL: https://issues.apache.org/jira/browse/IMPALA-

[jira] [Created] (IMPALA-7776) Fail queries where the sum of offset and limit exceed the max value of int64

Sahil Takiar created IMPALA-7776: Summary: Fail queries where the sum of offset and limit exceed the max value of int64 Key: IMPALA-7776 URL: https://issues.apache.org/jira/browse/IMPALA-7776

[jira] [Updated] (IMPALA-7754) Expressions sometimes not re-analyzed after rewrite

[ https://issues.apache.org/jira/browse/IMPALA-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7754: Description: The analyzer has a chain of rules which fire in order without (as noted above)

[jira] [Assigned] (IMPALA-7754) Expressions sometimes not re-analyzed after rewrite

[ https://issues.apache.org/jira/browse/IMPALA-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned IMPALA-7754: --- Assignee: (was: Paul Rogers) > Expressions sometimes not re-analyzed after rewrite >

[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=16657532#comment-16657532 ] Paul Rogers edited comment on IMPALA-7655 at 10/29/18 5:34 PM: --- Work on

[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=16659482#comment-16659482 ] Paul Rogers edited comment on IMPALA-7655 at 10/29/18 5:35 PM: --- To

[jira] [Commented] (IMPALA-7747) Review and modernize conditional function rewrites

[ https://issues.apache.org/jira/browse/IMPALA-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667528#comment-16667528 ] Paul Rogers commented on IMPALA-7747: - Other issues found in IMPALA-7655 and deferred: h4. Special

[jira] [Assigned] (IMPALA-7747) Clean up the Expression Rewriter

[ https://issues.apache.org/jira/browse/IMPALA-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned IMPALA-7747: --- Assignee: (was: Paul Rogers) Priority: Minor (was: Major) Description:

[jira] [Updated] (IMPALA-7764) Add test coverage for SentryProxy

[ https://issues.apache.org/jira/browse/IMPALA-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya updated IMPALA-7764: - Summary: Add test coverage for SentryProxy (was: SentryProxy needs unit tests) > Add test

[jira] [Created] (IMPALA-7778) RCFile parser ignores escape characters

Tim Armstrong created IMPALA-7778: - Summary: RCFile parser ignores escape characters Key: IMPALA-7778 URL: https://issues.apache.org/jira/browse/IMPALA-7778 Project: IMPALA Issue Type: Bug

[jira] [Commented] (IMPALA-7778) RCFile parser ignores escape characters

[ https://issues.apache.org/jira/browse/IMPALA-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667423#comment-16667423 ] Tim Armstrong commented on IMPALA-7778: --- Found this while adding tests for IMPALA-7586 > RCFile

[jira] [Updated] (IMPALA-7764) Add test coverage for SentryProxy

[ https://issues.apache.org/jira/browse/IMPALA-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fredy Wijaya updated IMPALA-7764: - Description: There are currently no unit tests in SentryProxy, which can lead to a number of

[jira] [Created] (IMPALA-7779) Parquet Scanner can write binary data into profile

Lars Volker created IMPALA-7779: --- Summary: Parquet Scanner can write binary data into profile Key: IMPALA-7779 URL: https://issues.apache.org/jira/browse/IMPALA-7779 Project: IMPALA Issue

[jira] [Assigned] (IMPALA-7769) Handle CAST(NULL AS type) in rewrites

[ https://issues.apache.org/jira/browse/IMPALA-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers reassigned IMPALA-7769: --- Assignee: (was: Paul Rogers) > Handle CAST(NULL AS type) in rewrites >

[jira] [Updated] (IMPALA-7769) Handle CAST(NULL AS type) in rewrites

[ https://issues.apache.org/jira/browse/IMPALA-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7769: Description: Consider the following query: {code:sql} SELECT IFNULL(NULL + 1, id) FROM

[jira] [Commented] (IMPALA-7776) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667413#comment-16667413 ] Sahil Takiar commented on IMPALA-7776: -- Whoops, not sure how that happened. Closing this as a

[jira] [Resolved] (IMPALA-7776) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar resolved IMPALA-7776. -- Resolution: Duplicate > Fail queries where the sum of offset and limit exceed the max value

[jira] [Commented] (IMPALA-7778) RCFile parser ignores escape characters

[ https://issues.apache.org/jira/browse/IMPALA-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667427#comment-16667427 ] Tim Armstrong commented on IMPALA-7778: --- I'm not assigning this a high priority because RCFile has

[jira] [Commented] (IMPALA-6042) Allow Impala shell to also use a global impalarc configuration

[ https://issues.apache.org/jira/browse/IMPALA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667434#comment-16667434 ] Ruslan Dautkhanov commented on IMPALA-6042: --- Another use case is to update PATH variable, to

[jira] [Updated] (IMPALA-7586) Incorrect results when querying primary = "\"" in Kudu and HBase

[ https://issues.apache.org/jira/browse/IMPALA-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7586: -- Summary: Incorrect results when querying primary = "\"" in Kudu and HBase (was: Incorrect

[jira] [Updated] (IMPALA-7769) Handle CAST(NULL AS type) in rewrites

[ https://issues.apache.org/jira/browse/IMPALA-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated IMPALA-7769: Summary: Handle CAST(NULL AS type) in rewrites (was: Constant folding sometimes introduces an

[jira] [Updated] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-: - Priority: Blocker (was: Major) > Fail queries where the sum of offset and limit exceed the max

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

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

[jira] [Updated] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-: - Issue Type: Bug (was: Improvement) > Fail queries where the sum of offset and limit exceed the

[jira] [Work started] (IMPALA-7727) failed compute stats child query status no longer propagates to parent query

[ https://issues.apache.org/jira/browse/IMPALA-7727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7727 started by Tim Armstrong. - > failed compute stats child query status no longer propagates to parent

[jira] [Updated] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated IMPALA-: - Affects Version/s: Impala 2.10.0 Impala 2.11.0

[jira] [Commented] (IMPALA-7565) Extends TAcceptQueueServer connection_setup_pool to be multi-threaded

[ https://issues.apache.org/jira/browse/IMPALA-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667572#comment-16667572 ] Tim Armstrong commented on IMPALA-7565: --- [~kwho] [~bikram.sngh91] [~lv] do we think anyone is

[jira] [Work started] (IMPALA-7586) Incorrect results when querying primary = "\"" in Kudu and HBase

[ https://issues.apache.org/jira/browse/IMPALA-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-7586 started by Tim Armstrong. - > Incorrect results when querying primary = "\"" in Kudu and HBase >

[jira] [Updated] (IMPALA-7662) test_parquet reads bad_magic_number.parquet without an error

[ https://issues.apache.org/jira/browse/IMPALA-7662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7662: -- Priority: Blocker (was: Critical) > test_parquet reads bad_magic_number.parquet without an

[jira] [Assigned] (IMPALA-2566) Result of casttochar() not handled properly in SQL operations

[ https://issues.apache.org/jira/browse/IMPALA-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned IMPALA-2566: - Assignee: Bikramjeet Vig > Result of casttochar() not handled properly in SQL

[jira] [Updated] (IMPALA-6853) COMPUTE STATS does an unnecessary REFRESH after writing to the Metastore

[ https://issues.apache.org/jira/browse/IMPALA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6853: -- Target Version: Impala 3.2.0, Impala 2.13.0 (was: Impala 2.13.0, Impala 3.1.0) > COMPUTE

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

[jira] [Updated] (IMPALA-6671) Metadata operations that modify a table blocks topic updates for other unrelated operations

[ https://issues.apache.org/jira/browse/IMPALA-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6671: -- Target Version: Product Backlog > Metadata operations that modify a table blocks topic

[jira] [Updated] (IMPALA-7777) Fail queries where the sum of offset and limit exceed the max value of int64

[ https://issues.apache.org/jira/browse/IMPALA-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-: -- Target Version: Impala 3.1.0 > Fail queries where the sum of offset and limit exceed the max

[jira] [Updated] (IMPALA-6955) Timeout when starting test_query_expiration custom cluster

[ https://issues.apache.org/jira/browse/IMPALA-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6955: -- Fix Version/s: (was: Not Applicable) > Timeout when starting test_query_expiration custom

[jira] [Updated] (IMPALA-6955) Timeout when starting test_query_expiration custom cluster

[ https://issues.apache.org/jira/browse/IMPALA-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-6955: -- Target Version: Impala 3.2.0 Labels: broken-build flaky (was: )

[jira] [Updated] (IMPALA-5765) Flaky tpc-ds data loading

[ https://issues.apache.org/jira/browse/IMPALA-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5765: -- Target Version: Impala 2.12.0, Product Backlog (was: Impala 2.12.0) Priority: Major

[jira] [Updated] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5746: -- Target Version: Product Backlog Per Michael's comment, it doesn't sound like we're going to

[jira] [Updated] (IMPALA-5746) Remote fragments continue to hold onto memory after stopping the coordinator daemon

[ https://issues.apache.org/jira/browse/IMPALA-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-5746: -- Target Version: Impala 3.2.0 (was: Product Backlog) > Remote fragments continue to hold onto

[jira] [Resolved] (IMPALA-5122) Impala and special character

[ https://issues.apache.org/jira/browse/IMPALA-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong resolved IMPALA-5122. --- Resolution: Invalid Hi [~Tina], I'm going to close this purely because we don't track

[jira] [Updated] (IMPALA-4018) Add support for SQL:2016 datetime templates/patterns/masks to CAST(... AS ... FORMAT )

[ https://issues.apache.org/jira/browse/IMPALA-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-4018: -- Target Version: Product Backlog > Add support for SQL:2016 datetime templates/patterns/masks