[jira] [Created] (HIVE-24153) distinct is not quite effective in table expression
Xinyu Wang created HIVE-24153: - Summary: distinct is not quite effective in table expression Key: HIVE-24153 URL: https://issues.apache.org/jira/browse/HIVE-24153 Project: Hive Issue Type: Bug Components: Query Planning Affects Versions: 3.1.1 Reporter: Xinyu Wang Below is an example: _t(id int, name string, comment string)._ _with cte as (_ _select distinct id, name, comment_ _from t_ _)_ _select count(*) from cte_ The result of the above query is larger than select count(distinct id, name, comment). In the result of EXPLAIN, PARTITION_ONLY_SHUFFLE is used. But for select count(distinct id, name, comment), SHUFFLE is used instead. Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24152) Comment out test until it is investigated.
Naveen Gangam created HIVE-24152: Summary: Comment out test until it is investigated. Key: HIVE-24152 URL: https://issues.apache.org/jira/browse/HIVE-24152 Project: Hive Issue Type: Sub-task Affects Versions: 4.0.0 Reporter: Naveen Gangam Assignee: Naveen Gangam Looks like this test was re-enabled between the time the precommits were run and it was committed (a few hours later). This is blocking all other commits. Commenting it out for now -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24151) MultiDelimitSerDe shifts data if strings contain non-ASCII characters
Ádám Szita created HIVE-24151: - Summary: MultiDelimitSerDe shifts data if strings contain non-ASCII characters Key: HIVE-24151 URL: https://issues.apache.org/jira/browse/HIVE-24151 Project: Hive Issue Type: Bug Reporter: Ádám Szita Assignee: Ádám Szita HIVE-22360 intended to fix another MultiDelimitSerde problem (with NULL last columns) but introduced a regression: the approach of the fix is pretty much all wrong, as the existing logic that operated on bytes got replaced by regex matcher logic which deals in character positions, rather than byte positions. As some non ASCII characters consist of more than 1 byte, the whole record may get shifted due to this. With this ticket I'm going to restore the old logic, and apply the proper fix on that, but keeping (and extending) the test cases added with HIVE-22360 so that we have a solution for both issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24150) Refactor CommitTxnRequest field order
Denys Kuzmenko created HIVE-24150: - Summary: Refactor CommitTxnRequest field order Key: HIVE-24150 URL: https://issues.apache.org/jira/browse/HIVE-24150 Project: Hive Issue Type: Bug Environment: Refactor CommitTxnRequest field order (keyValue and exclWriteEnabled). HIVE-24125 introduced backward incompatible change. Reporter: Denys Kuzmenko -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24149) HiveStreamingConnection doesn't close HMS connection
Attila Magyar created HIVE-24149: Summary: HiveStreamingConnection doesn't close HMS connection Key: HIVE-24149 URL: https://issues.apache.org/jira/browse/HIVE-24149 Project: Hive Issue Type: Bug Components: Hive Reporter: Attila Magyar Assignee: Attila Magyar Fix For: 4.0.0 There 3 HMS connections used by HiveStreamingConnection. One for TX one for hearbeat and for notifications. The close method only closes the first 2 leaving the last one open which eventually overloads HMS and it becomes unresponsive. -- This message was sent by Atlassian Jira (v8.3.4#803005)
