[jira] [Created] (HIVE-24222) Upgrade ORC to 1.5.12
Dongjoon Hyun created HIVE-24222: Summary: Upgrade ORC to 1.5.12 Key: HIVE-24222 URL: https://issues.apache.org/jira/browse/HIVE-24222 Project: Hive Issue Type: Bug Components: ORC Affects Versions: 4.0.0 Reporter: Dongjoon Hyun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24221) Use vectorizable expression to combine multiple columns in semijoin bloom filters
Stamatis Zampetakis created HIVE-24221: -- Summary: Use vectorizable expression to combine multiple columns in semijoin bloom filters Key: HIVE-24221 URL: https://issues.apache.org/jira/browse/HIVE-24221 Project: Hive Issue Type: Improvement Components: Query Planning Environment: Reporter: Stamatis Zampetakis Assignee: Stamatis Zampetakis Currently, multi-column semijoin reducers use an n-ary call to GenericUDFMurmurHash to combine multiple values into one, which is used as an entry to the bloom filter. However, there are no vectorized operators that treat n-ary inputs. The same goes for the vectorized implementation of GenericUDFMurmurHash introduced in HIVE-23976. The goal of this issue is to choose an alternative way to combine multiple values into one to pass in the bloom filter comprising only vectorized operators. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24220) Unable to reopen a closed bug report
Ankur Tagra created HIVE-24220: -- Summary: Unable to reopen a closed bug report Key: HIVE-24220 URL: https://issues.apache.org/jira/browse/HIVE-24220 Project: Hive Issue Type: Bug Reporter: Ankur Tagra -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24219) TestStreaming is flaky
Peter Varga created HIVE-24219: -- Summary: TestStreaming is flaky Key: HIVE-24219 URL: https://issues.apache.org/jira/browse/HIVE-24219 Project: Hive Issue Type: Bug Reporter: Peter Varga Seems like the HeartBeater threads did not get cleaned up and deadlocks itself with the transactional table cleanups http://ci.hive.apache.org/job/hive-flaky-check/119/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HIVE-24218) Drop table used by a materialized view
stephbat created HIVE-24218:
---
Summary: Drop table used by a materialized view
Key: HIVE-24218
URL: https://issues.apache.org/jira/browse/HIVE-24218
Project: Hive
Issue Type: Bug
Components: Hive
Affects Versions: 3.1.0
Reporter: stephbat
I have discovered that it's possible to drop a table used by a materialized
view. When I drop this table, the result is OK while I think this action should
be refused. When I check in the metastore database, I can see that the table
has been partially deleted (ie : the reference of the table still exists in
TBLS and in MV_TABLES_USED). This introduces an inconsistency in the metastore.
Steps to reproduced :
{code:java}
jdbc:hive2://localhost.> use use ptest2_db_dev;
No rows affected (0.067 seconds)
0: jdbc:hive2://localhost.> create table table_blocked (id string);
No rows affected (0.97 seconds)
0: jdbc:hive2://localhost.> desc table_blocked;
+---++--+
| col_name | data_type | comment |
+---++--+
| id| string | |
+---++--+
1 row selected (0.171 seconds)
0: jdbc:hive2://localhost.> create materialized view table_blocked_mv as select
* from table_blocked;
No rows affected (18.055 seconds)
0: jdbc:hive2://localhost.> desc table_blocked_mv;
+---++--+
| col_name | data_type | comment |
+---++--+
| id| string | |
+---++--+
1 row selected (0.316 seconds)
0: jdbc:hive2://localhost.> drop table table_blocked;
No rows affected (10.803 seconds)
0: jdbc:hive2://localhost.> desc table_blocked_mv;
+---++--+
| col_name | data_type | comment |
+---++--+
| id| string | |
+---++--+
1 row selected (0.222 seconds)
0: jdbc:hive2://localhost.> desc table_blocked;
Error: Error while compiling statement: FAILED: SemanticException Unable to
fetch table table_blocked. null (state=42000,code=4)
0: jdbc:hive2://localhost.> select * from table_blocked_mv;
Error: Error while compiling statement: FAILED: SemanticException Table
ptest2_db_dev.table_blocked not found when trying to obtain it to check
masking/filtering policies (state=42000,code=4)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
