[jira] [Created] (HIVE-27852) Backport of HIVE-27324: Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
Diksha created HIVE-27852: - Summary: Backport of HIVE-27324: Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value. Key: HIVE-27852 URL: https://issues.apache.org/jira/browse/HIVE-27852 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Fix For: 3.2.0, 3.0.0 Backport of HIVE-27324: Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27844) Multi destination queries giving error for Not in operators
Diksha created HIVE-27844: - Summary: Multi destination queries giving error for Not in operators Key: HIVE-27844 URL: https://issues.apache.org/jira/browse/HIVE-27844 Project: Hive Issue Type: Bug Reporter: Diksha When a filter operator is added to resolve the Not in bug for when cbo is disabled, multi insert queries like : from t3 b * INSERT OVERWRITE TABLE t4 * select * * where b.age not in * (select a.age * from t3 a * ) * order by age * INSERT OVERWRITE TABLE t5 * select * * where b.age in * (select c.age * from t3 c * ); give a runtime error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27822) Backport of HIVE-22336: Updates should be pushed to the Metastore backend DB before creating the notification event
Diksha created HIVE-27822: - Summary: Backport of HIVE-22336: Updates should be pushed to the Metastore backend DB before creating the notification event Key: HIVE-27822 URL: https://issues.apache.org/jira/browse/HIVE-27822 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 This is a backport of HIVE-22336: Updates should be pushed to the Metastore backend DB before creating the notification event -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27813) Backport of HIVE-25535: Control cleaning obsolete directories/files of a table via property
Diksha created HIVE-27813: - Summary: Backport of HIVE-25535: Control cleaning obsolete directories/files of a table via property Key: HIVE-27813 URL: https://issues.apache.org/jira/browse/HIVE-27813 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 This is a backport of HIVE-25535: Control cleaning obsolete directories/files of a table via property -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27812) Backport of HIVE-24138: Llap external client flow is broken due to netty shading
Diksha created HIVE-27812: - Summary: Backport of HIVE-24138: Llap external client flow is broken due to netty shading Key: HIVE-27812 URL: https://issues.apache.org/jira/browse/HIVE-27812 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 This is a backport of HIVE-24138: Llap external client flow is broken due to netty shading -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27811) Backport of HIVE-23023: MR compaction ignores column schema evolution
Diksha created HIVE-27811: - Summary: Backport of HIVE-23023: MR compaction ignores column schema evolution Key: HIVE-27811 URL: https://issues.apache.org/jira/browse/HIVE-27811 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 This is a backport of HIVE-23023: MR compaction ignores column schema evolution -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27810) Backport of HIVE-22593: Compaction fails on non bucketed table with data loaded inpath
Diksha created HIVE-27810: - Summary: Backport of HIVE-22593: Compaction fails on non bucketed table with data loaded inpath Key: HIVE-27810 URL: https://issues.apache.org/jira/browse/HIVE-27810 Project: Hive Issue Type: Sub-task Affects Versions: 3.2.0 Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 This is a backport of HIVE-22593: Compaction fails on non bucketed table with data loaded inpath -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27808) Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577
[ https://issues.apache.org/jira/browse/HIVE-27808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27808: -- Summary: Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577 (was: Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 ) > Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577 > - > > Key: HIVE-27808 > URL: https://issues.apache.org/jira/browse/HIVE-27808 > Project: Hive > Issue Type: Sub-task >Affects Versions: 3.2.0 >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > > Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 for all Unix timestamps > related JIRAs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27808) Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577
[ https://issues.apache.org/jira/browse/HIVE-27808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27808: -- Description: Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577 for all Unix timestamps related JIRAs. (was: Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 for all Unix timestamps related JIRAs.) > Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577 > - > > Key: HIVE-27808 > URL: https://issues.apache.org/jira/browse/HIVE-27808 > Project: Hive > Issue Type: Sub-task >Affects Versions: 3.2.0 >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: pull-request-available > Fix For: 3.2.0 > > > Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 , 25577 for all Unix > timestamps related JIRAs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27809) Backport of HIVE-21715: Adding a new partition specified by location (which is empty) leads to Exceptions
Diksha created HIVE-27809: - Summary: Backport of HIVE-21715: Adding a new partition specified by location (which is empty) leads to Exceptions Key: HIVE-27809 URL: https://issues.apache.org/jira/browse/HIVE-27809 Project: Hive Issue Type: Sub-task Affects Versions: 3.2.0 Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 Backport of HIVE-21715: Adding a new partition specified by location (which is empty) leads to Exceptions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27808) Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458
Diksha created HIVE-27808: - Summary: Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 Key: HIVE-27808 URL: https://issues.apache.org/jira/browse/HIVE-27808 Project: Hive Issue Type: Sub-task Affects Versions: 3.2.0 Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 Backport of HIVE-20082 ,22170 ,22331 , 24113 , 25458 for all Unix timestamps related JIRAs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27683) Incorrect result when filtering the table with default partition
[
https://issues.apache.org/jira/browse/HIVE-27683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diksha reassigned HIVE-27683:
-
Assignee: Diksha
> Incorrect result when filtering the table with default partition
>
>
> Key: HIVE-27683
> URL: https://issues.apache.org/jira/browse/HIVE-27683
> Project: Hive
> Issue Type: Bug
>Reporter: Zhihua Deng
>Assignee: Diksha
>Priority: Major
>
> Steps to repro:
> {noformat}
> create database pt;
> create table pt.alterdynamic_part_table(intcol string) partitioned by
> (partcol1 int, partcol2 int);
> insert into table pt.alterdynamic_part_table partition(partcol1, partcol2)
> select '2', 2, NULL;
> select intcol from pt.alterdynamic_part_table where (partcol1=2 and
> partcol2=1) or (partcol1=2 and partcol2='__HIVE_DEFAULT_PARTITION__');
> select intcol from pt.alterdynamic_part_table where
> partcol2='__HIVE_DEFAULT_PARTITION__';{noformat}
> The last two queries should return one line row instead of an empty result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27724) Upgrade ivy for CVE-2022-46751 fix
[ https://issues.apache.org/jira/browse/HIVE-27724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27724: -- Fix Version/s: 3.0.0 3.1.0 > Upgrade ivy for CVE-2022-46751 fix > -- > > Key: HIVE-27724 > URL: https://issues.apache.org/jira/browse/HIVE-27724 > Project: Hive > Issue Type: Task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Fix For: 3.1.0, 3.0.0 > > > Upgrade org.apache.ivy:ivy from 2.5.1 to 2.5.2 to fix the vulnerability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27724) Upgrade ivy for CVE-2022-46751 fix
Diksha created HIVE-27724: - Summary: Upgrade ivy for CVE-2022-46751 fix Key: HIVE-27724 URL: https://issues.apache.org/jira/browse/HIVE-27724 Project: Hive Issue Type: Task Reporter: Diksha Assignee: Diksha Upgrade org.apache.ivy:ivy from 2.5.1 to 2.5.2 to fix the vulnerability. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27700) Backport of HIVE-19081: Add partition should prevent loading acid files
Diksha created HIVE-27700: - Summary: Backport of HIVE-19081: Add partition should prevent loading acid files Key: HIVE-27700 URL: https://issues.apache.org/jira/browse/HIVE-27700 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha This is a Backport of HIVE-19081: Add partition should prevent loading acid files -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27699) Backport of HIVE-25458: Unix_timestamp() with string input give wrong result
Diksha created HIVE-27699: - Summary: Backport of HIVE-25458: Unix_timestamp() with string input give wrong result Key: HIVE-27699 URL: https://issues.apache.org/jira/browse/HIVE-27699 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha This is a backport of HIVE-25458: Unix_timestamp() with string input give wrong result -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-27324) Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
[
https://issues.apache.org/jira/browse/HIVE-27324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765949#comment-17765949
]
Diksha commented on HIVE-27324:
---
{quote}!sql_queries.png!
{quote}
> Hive query with NOT IN condition is giving incorrect results when the sub
> query table contains the null value.
> --
>
> Key: HIVE-27324
> URL: https://issues.apache.org/jira/browse/HIVE-27324
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: All Versions, 3.1.0
>Reporter: Shobika Selvaraj
>Assignee: Diksha
>Priority: Major
> Labels: pull-request-available
> Attachments: sql_queries.png
>
>
> Hive query giving empty results when the sub query table contains the null
> value.
> We encountered two issues here.
> 1) The query - "select * from t3 where age not in (select distinct(age) age
> from t1);" is giving empty results when the table t1 contains a null value.
> Disabling cbo didn't helped here.
> 2) Let's consider the table t3 has null value and table t1 doesn't have any
> null values. Now if we run the above query it is returning other data's but
> not the null value from t3. If we disable the cbo then it's giving result
> with null value.
>
> *REPRO STEPS WITH DETAILED EXPLANATION AS BELOW:*
> *FIRST ISSUE:*
> Create two tables and insert data with null values as below:
> ---
> create table t3 (id int,name string, age int);
>
> insert into t3
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45);
>
> create table t1 (id int,name string, age int);
> insert into t1
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> ---
>
> Then executed the below query:
> --
> select * from t3
> where age not in (select distinct(age) age from t1);
> --
>
> The result should be as below:
> {code:java}
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> | 9 | ron | 3 |
> | 10 | Sam | 22 |
> | 11 | nick | 19 |
> | 12 | fed | 18 |
> | 13 | kong | 13 |
> ++--+-+
> 5 rows selected (35.897 seconds) {code}
> But when we run the above query it is giving zero records:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t1);
> INFO : Compiling
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96):
> select * from t3
> where age not in (select distinct(age) age from t1)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> .
> INFO : Completed executing
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96);
> Time taken: 10.191 seconds
> INFO : OK
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> ++--+-+
> No rows selected (12.17 seconds) {code}
> The query works fine when we use nvl function or not null condition.
>
> So as a workaround we can use nvl function for both main and sub query as
> below:
> {code:java}
> select * from t3 where nvl(age,'-') not in (select distinct(nvl(age,'-')) age
> from t1); {code}
>
> *SECOND ISSUE:*
> Also while testing multiple scenario's i found one more issue as well.
> When the sub query table (t1) doesn't contain any null values then the query
> is giving result but it is ignoring the null values of the main table(t3) .
>
> For example: Created another table t4 and inserted the data's without any
> null values:
> create table t4 (id int,name string, age int);
> insert into t4
> values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> Now i tested with the below query and it gives 5 records. The count should be
> six and it omitted the null value of the table t3:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t4);
> INFO : Compiling
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c):
> select * from t3
> where age not in (select distinct(age) age from t4)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> ..
> INFO : Completed executing
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c);
>
[jira] (HIVE-27324) Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
[ https://issues.apache.org/jira/browse/HIVE-27324 ]
Diksha deleted comment on HIVE-27324:
---
was (Author: JIRAUSER298900):
{quote}!sql_queries.png!
{quote}
> Hive query with NOT IN condition is giving incorrect results when the sub
> query table contains the null value.
> --
>
> Key: HIVE-27324
> URL: https://issues.apache.org/jira/browse/HIVE-27324
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: All Versions, 3.1.0
>Reporter: Shobika Selvaraj
>Assignee: Diksha
>Priority: Major
> Labels: pull-request-available
> Attachments: sql_queries.png
>
>
> Hive query giving empty results when the sub query table contains the null
> value.
> We encountered two issues here.
> 1) The query - "select * from t3 where age not in (select distinct(age) age
> from t1);" is giving empty results when the table t1 contains a null value.
> Disabling cbo didn't helped here.
> 2) Let's consider the table t3 has null value and table t1 doesn't have any
> null values. Now if we run the above query it is returning other data's but
> not the null value from t3. If we disable the cbo then it's giving result
> with null value.
>
> *REPRO STEPS WITH DETAILED EXPLANATION AS BELOW:*
> *FIRST ISSUE:*
> Create two tables and insert data with null values as below:
> ---
> create table t3 (id int,name string, age int);
>
> insert into t3
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45);
>
> create table t1 (id int,name string, age int);
> insert into t1
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> ---
>
> Then executed the below query:
> --
> select * from t3
> where age not in (select distinct(age) age from t1);
> --
>
> The result should be as below:
> {code:java}
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> | 9 | ron | 3 |
> | 10 | Sam | 22 |
> | 11 | nick | 19 |
> | 12 | fed | 18 |
> | 13 | kong | 13 |
> ++--+-+
> 5 rows selected (35.897 seconds) {code}
> But when we run the above query it is giving zero records:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t1);
> INFO : Compiling
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96):
> select * from t3
> where age not in (select distinct(age) age from t1)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> .
> INFO : Completed executing
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96);
> Time taken: 10.191 seconds
> INFO : OK
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> ++--+-+
> No rows selected (12.17 seconds) {code}
> The query works fine when we use nvl function or not null condition.
>
> So as a workaround we can use nvl function for both main and sub query as
> below:
> {code:java}
> select * from t3 where nvl(age,'-') not in (select distinct(nvl(age,'-')) age
> from t1); {code}
>
> *SECOND ISSUE:*
> Also while testing multiple scenario's i found one more issue as well.
> When the sub query table (t1) doesn't contain any null values then the query
> is giving result but it is ignoring the null values of the main table(t3) .
>
> For example: Created another table t4 and inserted the data's without any
> null values:
> create table t4 (id int,name string, age int);
> insert into t4
> values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> Now i tested with the below query and it gives 5 records. The count should be
> six and it omitted the null value of the table t3:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t4);
> INFO : Compiling
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c):
> select * from t3
> where age not in (select distinct(age) age from t4)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> ..
> INFO : Completed executing
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c);
> Time taken: 17.724 seconds
> INFO : OK
>
[jira] [Updated] (HIVE-27324) Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
[
https://issues.apache.org/jira/browse/HIVE-27324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diksha updated HIVE-27324:
--
Attachment: sql_queries.png
> Hive query with NOT IN condition is giving incorrect results when the sub
> query table contains the null value.
> --
>
> Key: HIVE-27324
> URL: https://issues.apache.org/jira/browse/HIVE-27324
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: All Versions, 3.1.0
>Reporter: Shobika Selvaraj
>Assignee: Diksha
>Priority: Major
> Labels: pull-request-available
> Attachments: sql_queries.png
>
>
> Hive query giving empty results when the sub query table contains the null
> value.
> We encountered two issues here.
> 1) The query - "select * from t3 where age not in (select distinct(age) age
> from t1);" is giving empty results when the table t1 contains a null value.
> Disabling cbo didn't helped here.
> 2) Let's consider the table t3 has null value and table t1 doesn't have any
> null values. Now if we run the above query it is returning other data's but
> not the null value from t3. If we disable the cbo then it's giving result
> with null value.
>
> *REPRO STEPS WITH DETAILED EXPLANATION AS BELOW:*
> *FIRST ISSUE:*
> Create two tables and insert data with null values as below:
> ---
> create table t3 (id int,name string, age int);
>
> insert into t3
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45);
>
> create table t1 (id int,name string, age int);
> insert into t1
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> ---
>
> Then executed the below query:
> --
> select * from t3
> where age not in (select distinct(age) age from t1);
> --
>
> The result should be as below:
> {code:java}
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> | 9 | ron | 3 |
> | 10 | Sam | 22 |
> | 11 | nick | 19 |
> | 12 | fed | 18 |
> | 13 | kong | 13 |
> ++--+-+
> 5 rows selected (35.897 seconds) {code}
> But when we run the above query it is giving zero records:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t1);
> INFO : Compiling
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96):
> select * from t3
> where age not in (select distinct(age) age from t1)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> .
> INFO : Completed executing
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96);
> Time taken: 10.191 seconds
> INFO : OK
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> ++--+-+
> No rows selected (12.17 seconds) {code}
> The query works fine when we use nvl function or not null condition.
>
> So as a workaround we can use nvl function for both main and sub query as
> below:
> {code:java}
> select * from t3 where nvl(age,'-') not in (select distinct(nvl(age,'-')) age
> from t1); {code}
>
> *SECOND ISSUE:*
> Also while testing multiple scenario's i found one more issue as well.
> When the sub query table (t1) doesn't contain any null values then the query
> is giving result but it is ignoring the null values of the main table(t3) .
>
> For example: Created another table t4 and inserted the data's without any
> null values:
> create table t4 (id int,name string, age int);
> insert into t4
> values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> Now i tested with the below query and it gives 5 records. The count should be
> six and it omitted the null value of the table t3:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t4);
> INFO : Compiling
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c):
> select * from t3
> where age not in (select distinct(age) age from t4)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> ..
> INFO : Completed executing
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c);
> Time taken: 17.724 seconds
> INFO : OK
>
[jira] [Comment Edited] (HIVE-27324) Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
[ https://issues.apache.org/jira/browse/HIVE-27324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765948#comment-17765948 ] Diksha edited comment on HIVE-27324 at 9/16/23 11:03 AM: - sql queries ran in online sql compiler: create table t3 (id int,name varchar(255), age int); insert into t3 values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45); create table t4 (id int,name varchar(255), age int); insert into t4 values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23); create table t5 (id int,name varchar(255), ages int); insert into t5 values(1,'Sagar',23),(3,'Surya',NULL),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23); select * from t3 where age in (select distinct(age) age from t4) order by age ; select * from t3 where age not in (select distinct(age) age from t4 ) order by age ; select * from t3 where age not in (select distinct(ages) ages from t5 where t5.ages is not null) order by age ; select count(*) from t3 where age not in (select distinct(ages) ages from t5 ) order by age ; select count(*) from t3 where age not in (23,22, null ); select count(*) from t3 where age not in (select distinct(age)age from t3 t1 where t1.age > 10); Outputs: 6|Ramya|5 1|Sagar|23 3|Surya|23 5|Scott|23 7||23 8||23 4|Raman|45 14|hela|45 9|ron|3 13|kong|13 12|fed|18 11|nick|19 10|Sam|22 9|ron|3 13|kong|13 12|fed|18 11|nick|19 10|Sam|22 0 0 2 [Execution complete with exit code 0] was (Author: JIRAUSER298900): sql queries ran in online sql compiler: create table t3 (id int,name varchar(255), age int); insert into t3 values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45); create table t4 (id int,name varchar(255), age int); insert into t4 values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23); create table t5 (id int,name varchar(255), ages int); insert into t5 values(1,'Sagar',23),(3,'Surya',NULL),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23); select * from t3 where age in (select distinct(age) age from t4) order by age ; select * from t3 where age not in (select distinct(age) age from t4 ) order by age ; select * from t3 where age not in (select distinct(ages) ages from t5 where t5.ages is not null) order by age ; select count(*) from t3 where age not in (select distinct(ages) ages from t5 ) order by age ; select count(*) from t3 where age not in (23,22, null ); select count(*) from t3 where age not in (select distinct(age)age from t3 t1 where t1.age > 10); Outputs: 6|Ramya|5 1|Sagar|23 3|Surya|23 5|Scott|23 7||23 8||23 4|Raman|45 14|hela|45 9|ron|3 13|kong|13 12|fed|18 11|nick|19 10|Sam|22 9|ron|3 13|kong|13 12|fed|18 11|nick|19 10|Sam|22 0 0 2 [Execution complete with exit code 0] > Hive query with NOT IN condition is giving incorrect results when the sub > query table contains the null value. > -- > > Key: HIVE-27324 > URL: https://issues.apache.org/jira/browse/HIVE-27324 > Project: Hive > Issue Type: Bug > Components: Hive >Affects Versions: All Versions, 3.1.0 >Reporter: Shobika Selvaraj >Assignee: Diksha >Priority: Major > Labels: pull-request-available > > Hive query giving empty results when the sub query table contains the null > value. > We encountered two issues here. > 1) The query - "select * from t3 where age not in (select distinct(age) age > from t1);" is giving empty results when the table t1 contains a null value. > Disabling cbo didn't helped here. > 2) Let's consider the table t3 has null value and table t1 doesn't have any > null values. Now if we run the above query it is returning other data's but > not the null value from t3. If we disable the cbo then it's giving result > with null value. > > *REPRO STEPS WITH DETAILED EXPLANATION AS BELOW:* > *FIRST ISSUE:* > Create two tables and insert data with null values as below: > --- > create table t3 (id int,name string, age int); > > insert into t3 > values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45); > > create table t1 (id int,name string, age int); > insert into t1 > values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23); > --- > > Then
[jira] [Commented] (HIVE-27324) Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
[
https://issues.apache.org/jira/browse/HIVE-27324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765948#comment-17765948
]
Diksha commented on HIVE-27324:
---
sql queries ran in online sql compiler:
create table t3 (id int,name varchar(255), age int);
insert into t3
values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45);
create table t4 (id int,name varchar(255), age int);
insert into t4
values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
create table t5 (id int,name varchar(255), ages int);
insert into t5
values(1,'Sagar',23),(3,'Surya',NULL),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
select * from t3
where age in (select distinct(age) age from t4)
order by age ;
select * from t3
where age not in (select distinct(age) age from t4 )
order by age ;
select * from t3
where age not in (select distinct(ages) ages from t5 where t5.ages is not null)
order by age ;
select count(*) from t3
where age not in (select distinct(ages) ages from t5 )
order by age ;
select count(*) from t3
where age not in (23,22, null );
select count(*) from t3
where age not in (select distinct(age)age from t3 t1 where t1.age > 10);
Outputs:
6|Ramya|5
1|Sagar|23
3|Surya|23
5|Scott|23
7||23
8||23
4|Raman|45
14|hela|45
9|ron|3
13|kong|13
12|fed|18
11|nick|19
10|Sam|22
9|ron|3
13|kong|13
12|fed|18
11|nick|19
10|Sam|22
0
0
2
[Execution complete with exit code 0]
> Hive query with NOT IN condition is giving incorrect results when the sub
> query table contains the null value.
> --
>
> Key: HIVE-27324
> URL: https://issues.apache.org/jira/browse/HIVE-27324
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: All Versions, 3.1.0
>Reporter: Shobika Selvaraj
>Assignee: Diksha
>Priority: Major
> Labels: pull-request-available
>
> Hive query giving empty results when the sub query table contains the null
> value.
> We encountered two issues here.
> 1) The query - "select * from t3 where age not in (select distinct(age) age
> from t1);" is giving empty results when the table t1 contains a null value.
> Disabling cbo didn't helped here.
> 2) Let's consider the table t3 has null value and table t1 doesn't have any
> null values. Now if we run the above query it is returning other data's but
> not the null value from t3. If we disable the cbo then it's giving result
> with null value.
>
> *REPRO STEPS WITH DETAILED EXPLANATION AS BELOW:*
> *FIRST ISSUE:*
> Create two tables and insert data with null values as below:
> ---
> create table t3 (id int,name string, age int);
>
> insert into t3
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45);
>
> create table t1 (id int,name string, age int);
> insert into t1
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> ---
>
> Then executed the below query:
> --
> select * from t3
> where age not in (select distinct(age) age from t1);
> --
>
> The result should be as below:
> {code:java}
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> | 9 | ron | 3 |
> | 10 | Sam | 22 |
> | 11 | nick | 19 |
> | 12 | fed | 18 |
> | 13 | kong | 13 |
> ++--+-+
> 5 rows selected (35.897 seconds) {code}
> But when we run the above query it is giving zero records:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t1);
> INFO : Compiling
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96):
> select * from t3
> where age not in (select distinct(age) age from t1)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> .
> INFO : Completed executing
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96);
> Time taken: 10.191 seconds
> INFO : OK
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> ++--+-+
> No rows selected (12.17 seconds) {code}
> The query works fine when we use nvl function or not null condition.
>
> So as a workaround we can use nvl function for both main and sub query as
[jira] [Created] (HIVE-27666) Backport of HIVE-22903 : Vectorized row_number() resets the row number after one batch in case of constant expression in partition clause
Diksha created HIVE-27666: - Summary: Backport of HIVE-22903 : Vectorized row_number() resets the row number after one batch in case of constant expression in partition clause Key: HIVE-27666 URL: https://issues.apache.org/jira/browse/HIVE-27666 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-22903 : Vectorized row_number() resets the row number after one batch in case of constant expression in partition clause -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27574) Backport of HIVE-22661: Compaction fails on non bucketed table with data loaded inpath
Diksha created HIVE-27574: - Summary: Backport of HIVE-22661: Compaction fails on non bucketed table with data loaded inpath Key: HIVE-27574 URL: https://issues.apache.org/jira/browse/HIVE-27574 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-22661: Compaction fails on non bucketed table with data loaded inpath -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27561) Backport HIVE-22094 : queries failing with ClassCastException: hive.ql.exec.vector.DecimalColumnVector cannot be cast to hive.ql.exec.vector.Decimal64ColumnVector
Diksha created HIVE-27561: - Summary: Backport HIVE-22094 : queries failing with ClassCastException: hive.ql.exec.vector.DecimalColumnVector cannot be cast to hive.ql.exec.vector.Decimal64ColumnVector Key: HIVE-27561 URL: https://issues.apache.org/jira/browse/HIVE-27561 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha backport HIVE-22094 : queries failing with ClassCastException: hive.ql.exec.vector.DecimalColumnVector cannot be cast to hive.ql.exec.vector.Decimal64ColumnVector -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27501) CVE-2022-45868: upgraded h2database version to 2.2.220
[ https://issues.apache.org/jira/browse/HIVE-27501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27501: -- Description: The web-based admin console in H2 Database Engine through 2.1.214 can be started via the CLI with the argument -webAdminPassword, which allows the user to specify the password in cleartext for the web admin console. Consequently, a local user (or an attacker that has obtained local access through some means) would be able to discover the password by listing processes and their arguments. (was: The web-based admin console in H2 Database Engine through 2.1.214 can be started via the CLI with the argument -webAdminPassword, which allows the user to specify the password in cleartext for the web admin console. Consequently, a local user (or an attacker that has obtained local access through some means) would be able to discover the password by listing processes and their arguments. NOTE: the vendor states "This is not a vulnerability of H2 Console ... Passwords should never be passed on the command line and every qualified DBA or system administrator is expected to know that.") > CVE-2022-45868: upgraded h2database version to 2.2.220 > -- > > Key: HIVE-27501 > URL: https://issues.apache.org/jira/browse/HIVE-27501 > Project: Hive > Issue Type: Task >Reporter: Diksha >Assignee: Diksha >Priority: Major > > The web-based admin console in H2 Database Engine through 2.1.214 can be > started via the CLI with the argument -webAdminPassword, which allows the > user to specify the password in cleartext for the web admin console. > Consequently, a local user (or an attacker that has obtained local access > through some means) would be able to discover the password by listing > processes and their arguments. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27501) CVE-2022-45868: upgraded h2database version to 2.2.220
Diksha created HIVE-27501: - Summary: CVE-2022-45868: upgraded h2database version to 2.2.220 Key: HIVE-27501 URL: https://issues.apache.org/jira/browse/HIVE-27501 Project: Hive Issue Type: Task Reporter: Diksha Assignee: Diksha The web-based admin console in H2 Database Engine through 2.1.214 can be started via the CLI with the argument -webAdminPassword, which allows the user to specify the password in cleartext for the web admin console. Consequently, a local user (or an attacker that has obtained local access through some means) would be able to discover the password by listing processes and their arguments. NOTE: the vendor states "This is not a vulnerability of H2 Console ... Passwords should never be passed on the command line and every qualified DBA or system administrator is expected to know that." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27324) Hive query with NOT IN condition is giving incorrect results when the sub query table contains the null value.
[
https://issues.apache.org/jira/browse/HIVE-27324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diksha reassigned HIVE-27324:
-
Assignee: Diksha
> Hive query with NOT IN condition is giving incorrect results when the sub
> query table contains the null value.
> --
>
> Key: HIVE-27324
> URL: https://issues.apache.org/jira/browse/HIVE-27324
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: All Versions, 3.1.0
>Reporter: Shobika Selvaraj
>Assignee: Diksha
>Priority: Major
>
> Hive query giving empty results when the sub query table contains the null
> value.
> We encountered two issues here.
> 1) The query - "select * from t3 where age not in (select distinct(age) age
> from t1);" is giving empty results when the table t1 contains a null value.
> Disabling cbo didn't helped here.
> 2) Let's consider the table t3 has null value and table t1 doesn't have any
> null values. Now if we run the above query it is returning other data's but
> not the null value from t3. If we disable the cbo then it's giving result
> with null value.
>
> *REPRO STEPS WITH DETAILED EXPLANATION AS BELOW:*
> *FIRST ISSUE:*
> Create two tables and insert data with null values as below:
> ---
> create table t3 (id int,name string, age int);
>
> insert into t3
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23),(9,'ron',3),(10,'Sam',22),(11,'nick',19),(12,'fed',18),(13,'kong',13),(14,'hela',45);
>
> create table t1 (id int,name string, age int);
> insert into t1
> values(1,'Sagar',23),(2,'Sultan',NULL),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> ---
>
> Then executed the below query:
> --
> select * from t3
> where age not in (select distinct(age) age from t1);
> --
>
> The result should be as below:
> {code:java}
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> | 9 | ron | 3 |
> | 10 | Sam | 22 |
> | 11 | nick | 19 |
> | 12 | fed | 18 |
> | 13 | kong | 13 |
> ++--+-+
> 5 rows selected (35.897 seconds) {code}
> But when we run the above query it is giving zero records:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t1);
> INFO : Compiling
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96):
> select * from t3
> where age not in (select distinct(age) age from t1)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> .
> INFO : Completed executing
> command(queryId=hive_20230427164202_e25b671a-f3bd-41e4-b364-844466305d96);
> Time taken: 10.191 seconds
> INFO : OK
> ++--+-+
> | t3.id | t3.name | t3.age |
> ++--+-+
> ++--+-+
> No rows selected (12.17 seconds) {code}
> The query works fine when we use nvl function or not null condition.
>
> So as a workaround we can use nvl function for both main and sub query as
> below:
> {code:java}
> select * from t3 where nvl(age,'-') not in (select distinct(nvl(age,'-')) age
> from t1); {code}
>
> *SECOND ISSUE:*
> Also while testing multiple scenario's i found one more issue as well.
> When the sub query table (t1) doesn't contain any null values then the query
> is giving result but it is ignoring the null values of the main table(t3) .
>
> For example: Created another table t4 and inserted the data's without any
> null values:
> create table t4 (id int,name string, age int);
> insert into t4
> values(1,'Sagar',23),(3,'Surya',23),(4,'Raman',45),(5,'Scott',23),(6,'Ramya',5),(7,'',23),(8,'',23);
> Now i tested with the below query and it gives 5 records. The count should be
> six and it omitted the null value of the table t3:
> {code:java}
> 0: jdbc:hive2://zk0-shobia.lhlexkfu3vfebcezzj> select * from t3
> . . . . . . . . . . . . . . . . . . . . . . .> where age not in (select
> distinct(age) age from t4);
> INFO : Compiling
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c):
> select * from t3
> where age not in (select distinct(age) age from t4)
> INFO : Warning: Map Join MAPJOIN[37][bigTable=?] in task 'Map 1' is a cross
> product
> ..
> ..
> INFO : Completed executing
> command(queryId=hive_20230427164745_f20f47ce-614d-493d-8910-99a118de089c);
> Time taken: 17.724 seconds
> INFO : OK
> ++--+-+
> | t3.id | t3.name | t3.age |
>
[jira] [Work started] (HIVE-27456) CVE-2016-1000027: upgrade spring.framework version
[ https://issues.apache.org/jira/browse/HIVE-27456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-27456 started by Diksha. - > CVE-2016-127: upgrade spring.framework version > -- > > Key: HIVE-27456 > URL: https://issues.apache.org/jira/browse/HIVE-27456 > Project: Hive > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Diksha >Assignee: Diksha >Priority: Major > > upgrade spring.framework version to 6.0.0 for CVE-2016-127 fix -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27456) CVE-2016-1000027: upgrade spring.framework version
[ https://issues.apache.org/jira/browse/HIVE-27456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27456: -- Affects Version/s: 3.0.0 (was: 3.1.0) > CVE-2016-127: upgrade spring.framework version > -- > > Key: HIVE-27456 > URL: https://issues.apache.org/jira/browse/HIVE-27456 > Project: Hive > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Diksha >Assignee: Diksha >Priority: Major > > upgrade spring.framework version to 6.0.0 for CVE-2016-127 fix -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27456) CVE-2016-1000027: upgrade spring.framework version
[ https://issues.apache.org/jira/browse/HIVE-27456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27456: -- Description: upgrade spring.framework version to 6.0.0 for CVE-2016-127 fix (was: upgrade spring.framework version to 6.0.7 for CVE-2023-20860 fix) Summary: CVE-2016-127: upgrade spring.framework version (was: CVE-2023-20860: upgrade spring.framework version) > CVE-2016-127: upgrade spring.framework version > -- > > Key: HIVE-27456 > URL: https://issues.apache.org/jira/browse/HIVE-27456 > Project: Hive > Issue Type: Task >Affects Versions: 3.1.0 >Reporter: Diksha >Assignee: Diksha >Priority: Major > > upgrade spring.framework version to 6.0.0 for CVE-2016-127 fix -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27456) CVE-2023-20860: upgrade spring.framework version
Diksha created HIVE-27456: - Summary: CVE-2023-20860: upgrade spring.framework version Key: HIVE-27456 URL: https://issues.apache.org/jira/browse/HIVE-27456 Project: Hive Issue Type: Task Affects Versions: 3.1.0 Reporter: Diksha Assignee: Diksha upgrade spring.framework version to 6.0.7 for CVE-2023-20860 fix -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HIVE-27450) Upgrade snappy-java version to 1.1.10.1
[ https://issues.apache.org/jira/browse/HIVE-27450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-27450 started by Diksha. - > Upgrade snappy-java version to 1.1.10.1 > > > Key: HIVE-27450 > URL: https://issues.apache.org/jira/browse/HIVE-27450 > Project: Hive > Issue Type: Task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: pull-request-available > > Upgrade snappy-java version to 1.1.10.1 for CVE-2023-34455 fix -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27450) Upgrade snappy-java version to 1.1.10.1
Diksha created HIVE-27450: - Summary: Upgrade snappy-java version to 1.1.10.1 Key: HIVE-27450 URL: https://issues.apache.org/jira/browse/HIVE-27450 Project: Hive Issue Type: Task Reporter: Diksha Assignee: Diksha Upgrade snappy-java version to 1.1.10.1 for CVE-2023-34455 fix -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27411) Upgrade org.apache.calcite.avatica:avatica to 1.22.0 for CVE-2022-36364
Diksha created HIVE-27411: - Summary: Upgrade org.apache.calcite.avatica:avatica to 1.22.0 for CVE-2022-36364 Key: HIVE-27411 URL: https://issues.apache.org/jira/browse/HIVE-27411 Project: Hive Issue Type: Task Reporter: Diksha Upgrade org.apache.calcite.avatica:avatica to 1.22.0 for CVE-2022-36364 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27410) Calcite upgrade to 1.32.0 to fix CVE-2022-39135
Diksha created HIVE-27410: - Summary: Calcite upgrade to 1.32.0 to fix CVE-2022-39135 Key: HIVE-27410 URL: https://issues.apache.org/jira/browse/HIVE-27410 Project: Hive Issue Type: Task Reporter: Diksha In Apache Calcite prior to version 1.32.0 the SQL operators EXISTS_NODE, EXTRACT_XML, XML_TRANSFORM and EXTRACT_VALUE do not restrict XML External Entity references in their configuration, which makes them vulnerable to a potential XML External Entity (XXE) attack. Therefore any client exposing these operators, typically by using Oracle dialect (the first three) or MySQL dialect (the last one), is affected by this vulnerability (the extent of it will depend on the user under which the application is running). From Apache Calcite 1.32.0 onwards, Document Type Declarations and XML External Entity resolution are disabled on the impacted operators. It is recommended to upgrade to version 1.32.0 to fix CVE-2022-39135. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27389) Backport of HIVE-24882: Compaction task reattempt fails with FileAlreadyExistsException for DeleteEventWriter
Diksha created HIVE-27389: - Summary: Backport of HIVE-24882: Compaction task reattempt fails with FileAlreadyExistsException for DeleteEventWriter Key: HIVE-27389 URL: https://issues.apache.org/jira/browse/HIVE-27389 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-24882: Compaction task reattempt fails with FileAlreadyExistsException for DeleteEventWriter -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27388) Backport of HIVE-23058: Compaction task reattempt fails with FileAlreadyExistsException
Diksha created HIVE-27388: - Summary: Backport of HIVE-23058: Compaction task reattempt fails with FileAlreadyExistsException Key: HIVE-27388 URL: https://issues.apache.org/jira/browse/HIVE-27388 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-23058: Compaction task reattempt fails with FileAlreadyExistsException -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27387) Backport of HIVE-23046: Separate housekeeping thread from initiator flag
Diksha created HIVE-27387: - Summary: Backport of HIVE-23046: Separate housekeeping thread from initiator flag Key: HIVE-27387 URL: https://issues.apache.org/jira/browse/HIVE-27387 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-23046: Separate housekeeping thread from initiator flag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27385) Backport of HIVE-22099: Several date related UDFs can't handle Julian dates properly since HIVE-20007
Diksha created HIVE-27385: - Summary: Backport of HIVE-22099: Several date related UDFs can't handle Julian dates properly since HIVE-20007 Key: HIVE-27385 URL: https://issues.apache.org/jira/browse/HIVE-27385 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-22099: Several date related UDFs can't handle Julian dates properly since HIVE-20007 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27380) Backport of HIVE-24751: Kill trigger in workload manager fails with "No privilege" exception when authorization is disabled.
Diksha created HIVE-27380: - Summary: Backport of HIVE-24751: Kill trigger in workload manager fails with "No privilege" exception when authorization is disabled. Key: HIVE-27380 URL: https://issues.apache.org/jira/browse/HIVE-27380 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-24751: Kill trigger in workload manager fails with "No privilege" exception when authorization is disabled. it is not checked whether authorization is enabled or not for Kill Query access. This causes Workload Manager thread to end up with No privilege Exception when trying to kill a query in an environment where authorization is disabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27379) Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state
Diksha created HIVE-27379: - Summary: Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state Key: HIVE-27379 URL: https://issues.apache.org/jira/browse/HIVE-27379 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-22566: Drop table involved in materialized view leaves the table in inconsistent state -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27378) Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly
Diksha created HIVE-27378: - Summary: Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly Key: HIVE-27378 URL: https://issues.apache.org/jira/browse/HIVE-27378 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-19133: HS2 WebUI phase-wise performance metrics not showing correctly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27377) Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action
Diksha created HIVE-27377: - Summary: Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action Key: HIVE-27377 URL: https://issues.apache.org/jira/browse/HIVE-27377 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-24803: WorkloadManager doesn't update allocation and metrics after Kill Trigger action -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27376) Backport of HIVE-24964: Backport HIVE-22453: Describe table unnecessarily fetches partitions
[ https://issues.apache.org/jira/browse/HIVE-27376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27376: -- Fix Version/s: (was: 3.2.0) Target Version/s: 3.2.0 > Backport of HIVE-24964: Backport HIVE-22453: Describe table unnecessarily > fetches partitions > > > Key: HIVE-27376 > URL: https://issues.apache.org/jira/browse/HIVE-27376 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > > Backport of HIVE-24964: Backport HIVE-22453: Describe table unnecessarily > fetches partitions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27376) Backport of HIVE-24964: Backport HIVE-22453: Describe table unnecessarily fetches partitions
Diksha created HIVE-27376: - Summary: Backport of HIVE-24964: Backport HIVE-22453: Describe table unnecessarily fetches partitions Key: HIVE-27376 URL: https://issues.apache.org/jira/browse/HIVE-27376 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Fix For: 3.2.0 Backport of HIVE-24964: Backport HIVE-22453: Describe table unnecessarily fetches partitions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27335) Backport of HIVE-25468: Authorization for Create/Drop functions in HMS(Saihemanth Gantasala via Naveen Gangam)
Diksha created HIVE-27335: - Summary: Backport of HIVE-25468: Authorization for Create/Drop functions in HMS(Saihemanth Gantasala via Naveen Gangam) Key: HIVE-27335 URL: https://issues.apache.org/jira/browse/HIVE-27335 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-25468: Authorization for Create/Drop functions in HMS(Saihemanth Gantasala via Naveen Gangam) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27334) Backport of HIVE-25726: Upgrade velocity to 2.3 due to CVE-2020-13936 (Sourabh Goyal via Naveen Gangam)
Diksha created HIVE-27334: - Summary: Backport of HIVE-25726: Upgrade velocity to 2.3 due to CVE-2020-13936 (Sourabh Goyal via Naveen Gangam) Key: HIVE-27334 URL: https://issues.apache.org/jira/browse/HIVE-27334 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-25726: Upgrade velocity to 2.3 due to CVE-2020-13936 (Sourabh Goyal via Naveen Gangam) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27333) Backport of HIVE-25547: Alter view as Select statement should create Authorizable events in HS2(Saihemanth reviewed by Naveen Gangam)
Diksha created HIVE-27333: - Summary: Backport of HIVE-25547: Alter view as Select statement should create Authorizable events in HS2(Saihemanth reviewed by Naveen Gangam) Key: HIVE-27333 URL: https://issues.apache.org/jira/browse/HIVE-27333 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-25547: Alter view as Select statement should create Authorizable events in HS2(Saihemanth reviewed by Naveen Gangam) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27314) Backport of HIVE-25600: Compaction job creates redundant base/delta folder within base/delta folder
Diksha created HIVE-27314: - Summary: Backport of HIVE-25600: Compaction job creates redundant base/delta folder within base/delta folder Key: HIVE-27314 URL: https://issues.apache.org/jira/browse/HIVE-27314 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-25600: Compaction job creates redundant base/delta folder within base/delta folder -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27313) Backport of HIVE-24324: Remove deprecated API usage from Avro
Diksha created HIVE-27313: - Summary: Backport of HIVE-24324: Remove deprecated API usage from Avro Key: HIVE-27313 URL: https://issues.apache.org/jira/browse/HIVE-27313 Project: Hive Issue Type: Sub-task Reporter: Diksha Assignee: Diksha Backport of HIVE-24324: Remove deprecated API usage from Avro -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27312) Backport of HIVE-24965: Describe table partition stats fetch should be configurable
[ https://issues.apache.org/jira/browse/HIVE-27312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha reassigned HIVE-27312: - Assignee: Diksha > Backport of HIVE-24965: Describe table partition stats fetch should be > configurable > --- > > Key: HIVE-27312 > URL: https://issues.apache.org/jira/browse/HIVE-27312 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > > Backport of HIVE-24965: Describe table partition stats fetch should be > configurable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27312) Backport of HIVE-24965: Describe table partition stats fetch should be configurable
Diksha created HIVE-27312: - Summary: Backport of HIVE-24965: Describe table partition stats fetch should be configurable Key: HIVE-27312 URL: https://issues.apache.org/jira/browse/HIVE-27312 Project: Hive Issue Type: Sub-task Reporter: Diksha Backport of HIVE-24965: Describe table partition stats fetch should be configurable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27248) Backport of HIVE-24653: Race condition between compactor marker generation and get splits
[ https://issues.apache.org/jira/browse/HIVE-27248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha reassigned HIVE-27248: - Assignee: Diksha > Backport of HIVE-24653: Race condition between compactor marker generation > and get splits > - > > Key: HIVE-27248 > URL: https://issues.apache.org/jira/browse/HIVE-27248 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > > Backport of HIVE-24653: Race condition between compactor marker generation > and get splits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27248) Backport of HIVE-24653: Race condition between compactor marker generation and get splits
Diksha created HIVE-27248: - Summary: Backport of HIVE-24653: Race condition between compactor marker generation and get splits Key: HIVE-27248 URL: https://issues.apache.org/jira/browse/HIVE-27248 Project: Hive Issue Type: Sub-task Reporter: Diksha Backport of HIVE-24653: Race condition between compactor marker generation and get splits -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27247) Backport of HIVE-24436: Fix Avro NULL_DEFAULT_VALUE compatibility issue
Diksha created HIVE-27247: - Summary: Backport of HIVE-24436: Fix Avro NULL_DEFAULT_VALUE compatibility issue Key: HIVE-27247 URL: https://issues.apache.org/jira/browse/HIVE-27247 Project: Hive Issue Type: Sub-task Components: Hive Reporter: Diksha Assignee: Diksha Backport of HIVE-24436: Fix Avro NULL_DEFAULT_VALUE compatibility issue -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27214) Backport of HIVE-24414: Backport HIVE-19662 to branch-3.1
[ https://issues.apache.org/jira/browse/HIVE-27214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha reassigned HIVE-27214: - Assignee: Diksha > Backport of HIVE-24414: Backport HIVE-19662 to branch-3.1 > - > > Key: HIVE-27214 > URL: https://issues.apache.org/jira/browse/HIVE-27214 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27058) Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1
[ https://issues.apache.org/jira/browse/HIVE-27058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27058: -- Description: Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 > Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 > - > > Key: HIVE-27058 > URL: https://issues.apache.org/jira/browse/HIVE-27058 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: hive-3.2.0-must > > Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27212) Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1
[ https://issues.apache.org/jira/browse/HIVE-27212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27212: -- Parent: HIVE-26752 Issue Type: Sub-task (was: Task) > Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 > - > > Key: HIVE-27212 > URL: https://issues.apache.org/jira/browse/HIVE-27212 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Priority: Major > > Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27205) Update jackson-databind for CVE fix for CVE-2022-42003
[ https://issues.apache.org/jira/browse/HIVE-27205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha reassigned HIVE-27205: - > Update jackson-databind for CVE fix for CVE-2022-42003 > -- > > Key: HIVE-27205 > URL: https://issues.apache.org/jira/browse/HIVE-27205 > Project: Hive > Issue Type: Task >Reporter: Diksha >Assignee: Diksha >Priority: Major > > Update jackson-databind for CVE fix for CVE-2022-42003 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27058) Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1
[ https://issues.apache.org/jira/browse/HIVE-27058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha updated HIVE-27058: -- Labels: hive-3.2.0-must (was: ) > Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 > - > > Key: HIVE-27058 > URL: https://issues.apache.org/jira/browse/HIVE-27058 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > Labels: hive-3.2.0-must > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (HIVE-27058) Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1
[ https://issues.apache.org/jira/browse/HIVE-27058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diksha reassigned HIVE-27058: - > Backport of HIVE-24316: Upgrade ORC from 1.5.6 to 1.5.8 in branch-3.1 > - > > Key: HIVE-27058 > URL: https://issues.apache.org/jira/browse/HIVE-27058 > Project: Hive > Issue Type: Sub-task >Reporter: Diksha >Assignee: Diksha >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
