[jira] [Created] (HIVE-26503) Hive JDBC Storage Handler: Failed to create jdbc table with hive.sql.query

2022-08-30 Thread zhangbutao (Jira) 
zhangbutao created HIVE-26503:
-

 Summary: Hive JDBC Storage Handler: Failed to create jdbc table 
with hive.sql.query
 Key: HIVE-26503
 URL: https://issues.apache.org/jira/browse/HIVE-26503
 Project: Hive
  Issue Type: Bug
  Components: JDBC storage handler
Affects Versions: 4.0.0-alpha-1, 4.0.0-alpha-2
Reporter: zhangbutao






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HIVE-26504) User is not able to drop table

2022-08-30 Thread Jira 
László Végh created HIVE-26504:
--

 Summary: User is not able to drop table
 Key: HIVE-26504
 URL: https://issues.apache.org/jira/browse/HIVE-26504
 Project: Hive
  Issue Type: Bug
  Components: Hive
Reporter: László Végh


Hive won't store anything in *TAB_COL_STATS* for partitioned table, whereas 
impala stores complete column stats in TAB_COL_STATS for partitioned table. 
Deleting entries in TAB_COL_STATS is based on (DB_NAME, TABLE_NAME), not by 
TBL_ID. Renamed tables were having old names in TAB_COL_STATS.

To Repro:
{code:java}
beeline:
set hive.create.as.insert.only=false;
set hive.create.as.acid=false;
create table testes.table_name_with_partition (id tinyint, name string) 
partitioned by (col_to_partition bigint) stored as parquet;
insert into testes.table_name_with_partition (id, name, col_to_partition) 
values (1, "a", 2020), (2, "b", 2021), (3, "c", 2022);

impala:
compute stats testes.table_name_with_partition; -- backend shows new entries in 
TAB_COL_STATS

beeline:
alter table testes.table_name_with_partition rename to 
testes2.table_that_cant_be_droped;
drop table testes2.table_that_cant_be_droped; -- This fails with 
TAB_COL_STATS_fkey constraint violation.
{code}
Exception trace for drop table failure
{code:java}
Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on table 
"TBLS" violates foreign key constraint "TAB_COL_STATS_fkey" on table 
"TAB_COL_STATS"
  Detail: Key (TBL_ID)=(19816) is still referenced from table "TAB_COL_STATS".
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2532)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2267)
... 50 more
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HIVE-26505) Case When Some result data is lost when there are common column conditions and partitioned column conditions

2022-08-30 Thread GuangMing Lu (Jira) 
GuangMing Lu created HIVE-26505:
---

 Summary: Case When Some result data is lost when there are common 
column conditions and partitioned column conditions 
 Key: HIVE-26505
 URL: https://issues.apache.org/jira/browse/HIVE-26505
 Project: Hive
  Issue Type: Bug
  Components: Hive
Affects Versions: 4.0.0-alpha-1, 3.1.0
Reporter: GuangMing Lu


insert into test0831 values ('a', '2022-08-23'),('c', '2022-08-24'),('d', 
'2022-08-244');
insert into test0831 values ('a', '2022-08-24'),('b', '2022-08-24');

select * from test0831;
+-+--+
| test0831.id | test0831.cp  |
+-+--+
| a           | 2022-08-23   |
| b           | 2022-08-23   |
| a           | 2022-08-23   |
| c           | 2022-08-24   |
| d           | 2022-08-24   |
+-+--+

select * from test0831 where (case when id='a' and cp='2022-08-24' then 1 else 
0 end)=0;

+--+--+
| test0830.id  | test0830.cp  |
+--+--+
| a            | 2022-08-23   |
| c            | 2022-08-23   |
| d            | 2022-08-23   |
+--+--+



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HIVE-26506) HiveIcebergVectorizedRecordReader doesn't set the selected array

2022-08-30 Thread Jira 
Ádám Szita created HIVE-26506:
-

 Summary: HiveIcebergVectorizedRecordReader doesn't set the 
selected array
 Key: HIVE-26506
 URL: https://issues.apache.org/jira/browse/HIVE-26506
 Project: Hive
  Issue Type: Bug
Reporter: Ádám Szita
Assignee: Ádám Szita


HiveIcebergVectorizedRecordReader currently only sets {{selectedInUse}} but not 
{{selected}} that can cause the following exceptions where ORC row level 
filtering kicks in:
{code:java}
Caused by: java.lang.RuntimeException: all is not in sort order and unique
at 
org.apache.hadoop.hive.ql.exec.vector.expressions.FilterExprOrExpr.subtract(FilterExprOrExpr.java:69)
at 
org.apache.hadoop.hive.ql.exec.vector.expressions.FilterExprOrExpr.evaluate(FilterExprOrExpr.java:195)
at 
org.apache.hadoop.hive.ql.exec.vector.expressions.FilterExprAndExpr.evaluate(FilterExprAndExpr.java:42)
at 
org.apache.hadoop.hive.ql.exec.vector.VectorFilterOperator.process(VectorFilterOperator.java:125)
at 
org.apache.hadoop.hive.ql.exec.Operator.vectorForward(Operator.java:968)
at 
org.apache.hadoop.hive.ql.exec.TableScanOperator.process(TableScanOperator.java:172)
at 
org.apache.hadoop.hive.ql.exec.vector.VectorMapOperator.deliverVectorizedRowBatch(VectorMapOperator.java:809)
at 
org.apache.hadoop.hive.ql.exec.vector.VectorMapOperator.process(VectorMapOperator.java:842)
 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)