[jira] [Updated] (HIVE-28167) Full table deletion fails when converting to truncate for Iceberg and ACID tables
[
https://issues.apache.org/jira/browse/HIVE-28167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sourabh Badhya updated HIVE-28167:
--
Summary: Full table deletion fails when converting to truncate for Iceberg
and ACID tables (was: HIVE-28167: Full table deletion fails when converting to
truncate for Iceberg and ACID tables)
> Full table deletion fails when converting to truncate for Iceberg and ACID
> tables
> -
>
> Key: HIVE-28167
> URL: https://issues.apache.org/jira/browse/HIVE-28167
> Project: Hive
> Issue Type: Bug
>Reporter: Sourabh Badhya
>Assignee: Sourabh Badhya
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> A simple repro -
> {code:java}
> create table ice01 (id int, key int) stored by iceberg stored as orc
> tblproperties ('format-version'='2', 'write.delete.mode'='copy-on-write');
> insert into ice01 values (1,1),(2,1),(3,1),(4,1);
> insert into ice01 values (1,2),(2,2),(3,2),(4,2);
> insert into ice01 values (1,3),(2,3),(3,3),(4,3);
> insert into ice01 values (1,4),(2,4),(3,4),(4,4);
> insert into ice01 values (1,5),(2,5),(3,5),(4,5);
> explain analyze delete from ice01;
> delete from ice01;
> select count(*) from ice01;
> select * from ice01;
> describe formatted ice01; {code}
> The solution is to convert full table deletion to a truncate operation on the
> table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (HIVE-28167) HIVE-28167: Full table deletion fails when converting to truncate for Iceberg and ACID tables
[
https://issues.apache.org/jira/browse/HIVE-28167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sourabh Badhya resolved HIVE-28167.
---
Fix Version/s: 4.1.0
Resolution: Fixed
Merged to master.
Thanks [~dkuzmenko] for the reviews.
> HIVE-28167: Full table deletion fails when converting to truncate for Iceberg
> and ACID tables
> -
>
> Key: HIVE-28167
> URL: https://issues.apache.org/jira/browse/HIVE-28167
> Project: Hive
> Issue Type: Bug
>Reporter: Sourabh Badhya
>Assignee: Sourabh Badhya
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> A simple repro -
> {code:java}
> create table ice01 (id int, key int) stored by iceberg stored as orc
> tblproperties ('format-version'='2', 'write.delete.mode'='copy-on-write');
> insert into ice01 values (1,1),(2,1),(3,1),(4,1);
> insert into ice01 values (1,2),(2,2),(3,2),(4,2);
> insert into ice01 values (1,3),(2,3),(3,3),(4,3);
> insert into ice01 values (1,4),(2,4),(3,4),(4,4);
> insert into ice01 values (1,5),(2,5),(3,5),(4,5);
> explain analyze delete from ice01;
> delete from ice01;
> select count(*) from ice01;
> select * from ice01;
> describe formatted ice01; {code}
> The solution is to convert full table deletion to a truncate operation on the
> table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-28129) Execute statement doesnot report the correct query string information
[ https://issues.apache.org/jira/browse/HIVE-28129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Kumar Thangarajan updated HIVE-28129: Fix Version/s: 4.0.0 > Execute statement doesnot report the correct query string information > - > > Key: HIVE-28129 > URL: https://issues.apache.org/jira/browse/HIVE-28129 > Project: Hive > Issue Type: Bug >Reporter: Ramesh Kumar Thangarajan >Assignee: Ramesh Kumar Thangarajan >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > > Execute statement does not report the correct query type information. > It inherits the sql statement type of the subsequent queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-28129) Execute statement doesnot report the correct query string information
[ https://issues.apache.org/jira/browse/HIVE-28129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Kumar Thangarajan resolved HIVE-28129. - Resolution: Fixed > Execute statement doesnot report the correct query string information > - > > Key: HIVE-28129 > URL: https://issues.apache.org/jira/browse/HIVE-28129 > Project: Hive > Issue Type: Bug >Reporter: Ramesh Kumar Thangarajan >Assignee: Ramesh Kumar Thangarajan >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > > Execute statement does not report the correct query type information. > It inherits the sql statement type of the subsequent queries. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28171) Active queries API does not provide query information if they are still pending
[ https://issues.apache.org/jira/browse/HIVE-28171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Kumar Thangarajan updated HIVE-28171: Summary: Active queries API does not provide query information if they are still pending (was: Active queries API does not provide information on the queries if they are still pending) > Active queries API does not provide query information if they are still > pending > --- > > Key: HIVE-28171 > URL: https://issues.apache.org/jira/browse/HIVE-28171 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Ramesh Kumar Thangarajan >Assignee: Ramesh Kumar Thangarajan >Priority: Major > > Active queries API does not provide information on the queries if they are > still pending. SO we will never know what query is pending when we query this > API endpoint. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28171) Active queries API does not provide query information if they are still pending
[ https://issues.apache.org/jira/browse/HIVE-28171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-28171: -- Labels: pull-request-available (was: ) > Active queries API does not provide query information if they are still > pending > --- > > Key: HIVE-28171 > URL: https://issues.apache.org/jira/browse/HIVE-28171 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Ramesh Kumar Thangarajan >Assignee: Ramesh Kumar Thangarajan >Priority: Major > Labels: pull-request-available > > Active queries API does not provide information on the queries if they are > still pending. SO we will never know what query is pending when we query this > API endpoint. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-28171) Active queries API does not provide information on the queries if they are still pending
Ramesh Kumar Thangarajan created HIVE-28171: --- Summary: Active queries API does not provide information on the queries if they are still pending Key: HIVE-28171 URL: https://issues.apache.org/jira/browse/HIVE-28171 Project: Hive Issue Type: Bug Components: HiveServer2 Reporter: Ramesh Kumar Thangarajan Assignee: Ramesh Kumar Thangarajan Active queries API does not provide information on the queries if they are still pending. SO we will never know what query is pending when we query this API endpoint. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28167) HIVE-28167: Full table deletion fails when converting to truncate for Iceberg and ACID tables
[
https://issues.apache.org/jira/browse/HIVE-28167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sourabh Badhya updated HIVE-28167:
--
Summary: HIVE-28167: Full table deletion fails when converting to truncate
for Iceberg and ACID tables (was: Iceberg: Full table deletion fails when
using Copy-on-write)
> HIVE-28167: Full table deletion fails when converting to truncate for Iceberg
> and ACID tables
> -
>
> Key: HIVE-28167
> URL: https://issues.apache.org/jira/browse/HIVE-28167
> Project: Hive
> Issue Type: Bug
>Reporter: Sourabh Badhya
>Assignee: Sourabh Badhya
>Priority: Major
> Labels: pull-request-available
>
> A simple repro -
> {code:java}
> create table ice01 (id int, key int) stored by iceberg stored as orc
> tblproperties ('format-version'='2', 'write.delete.mode'='copy-on-write');
> insert into ice01 values (1,1),(2,1),(3,1),(4,1);
> insert into ice01 values (1,2),(2,2),(3,2),(4,2);
> insert into ice01 values (1,3),(2,3),(3,3),(4,3);
> insert into ice01 values (1,4),(2,4),(3,4),(4,4);
> insert into ice01 values (1,5),(2,5),(3,5),(4,5);
> explain analyze delete from ice01;
> delete from ice01;
> select count(*) from ice01;
> select * from ice01;
> describe formatted ice01; {code}
> The solution is to convert full table deletion to a truncate operation on the
> table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-28170) Implement drop stats
[ https://issues.apache.org/jira/browse/HIVE-28170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-28170: -- Labels: pull-request-available (was: ) > Implement drop stats > > > Key: HIVE-28170 > URL: https://issues.apache.org/jira/browse/HIVE-28170 > Project: Hive > Issue Type: Task >Reporter: Ramesh Kumar Thangarajan >Assignee: Ramesh Kumar Thangarajan >Priority: Major > Labels: pull-request-available > > We need a way to drop the stats associated with the table/partition and its > columns. This can help a lot in migration or replication where the stats data > take huge time to copy. Particularly when the table is partitioned, we have > stats rows for each table, partition, column combination, which can get huge > when the number of partitions is huge. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-28170) Implement drop stats
[ https://issues.apache.org/jira/browse/HIVE-28170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Kumar Thangarajan updated HIVE-28170: Description: We need a way to drop the stats associated with the table/partition and its columns. This can help a lot in migration or replication where the stats data take huge time to copy. Particularly when the table is partitioned, we have stats rows for each table, partition, column combination, which can get huge when the number of partitions is huge. > Implement drop stats > > > Key: HIVE-28170 > URL: https://issues.apache.org/jira/browse/HIVE-28170 > Project: Hive > Issue Type: Task >Reporter: Ramesh Kumar Thangarajan >Assignee: Ramesh Kumar Thangarajan >Priority: Major > > We need a way to drop the stats associated with the table/partition and its > columns. This can help a lot in migration or replication where the stats data > take huge time to copy. Particularly when the table is partitioned, we have > stats rows for each table, partition, column combination, which can get huge > when the number of partitions is huge. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-28170) Implement drop stats
Ramesh Kumar Thangarajan created HIVE-28170: --- Summary: Implement drop stats Key: HIVE-28170 URL: https://issues.apache.org/jira/browse/HIVE-28170 Project: Hive Issue Type: Task Reporter: Ramesh Kumar Thangarajan Assignee: Ramesh Kumar Thangarajan -- This message was sent by Atlassian Jira (v8.20.10#820010)
