[jira] [Resolved] (HIVE-27575) MASK_HASH UDF generate a log per row
[
https://issues.apache.org/jira/browse/HIVE-27575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HIVE-27575.
-
Fix Version/s: 4.0.0
Resolution: Fixed
> MASK_HASH UDF generate a log per row
>
>
> Key: HIVE-27575
> URL: https://issues.apache.org/jira/browse/HIVE-27575
> Project: Hive
> Issue Type: Improvement
> Components: UDF
>Affects Versions: 4.0.0-alpha-2
>Reporter: okumin
>Assignee: okumin
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Hive 4 started generating too many logs since we merged the following patch.
> https://issues.apache.org/jira/browse/HIVE-26724
> {code:txt}
> $ ./bin/logs hive-hiveserver2-859d7686f7-8tkj8 | grep MaskHashTransformer
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,360 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-27575) MASK_HASH UDF generate a log per row
[
https://issues.apache.org/jira/browse/HIVE-27575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752426#comment-17752426
]
Ayush Saxena commented on HIVE-27575:
-
Committed to master.
Thanx [~okumin] for the contribution!!!
> MASK_HASH UDF generate a log per row
>
>
> Key: HIVE-27575
> URL: https://issues.apache.org/jira/browse/HIVE-27575
> Project: Hive
> Issue Type: Improvement
> Components: UDF
>Affects Versions: 4.0.0-alpha-2
>Reporter: okumin
>Assignee: okumin
>Priority: Major
> Labels: pull-request-available
>
> Hive 4 started generating too many logs since we merged the following patch.
> https://issues.apache.org/jira/browse/HIVE-26724
> {code:txt}
> $ ./bin/logs hive-hiveserver2-859d7686f7-8tkj8 | grep MaskHashTransformer
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,360 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> hive-hiveserver2-859d7686f7-8tkj8: 2023-08-07T21:55:50,361 INFO
> [HiveServer2-Background-Pool: Thread-90] generic.MaskHashTransformer: Using
> SHA256 for masking
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-27588) Char set for few columns in HMS schema for fresh install and upgrade case are not in sync
[ https://issues.apache.org/jira/browse/HIVE-27588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pravin Sinha updated HIVE-27588: Description: ||Table||Column||Fresh Install||Upgrade case|| |PARTITION_EVENTS|CAT_NAME|`CAT_NAME` varchar(256) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL|`CAT_NAME` varchar(256) DEFAULT NULL| |SERDES|DESCRIPTION|`DESCRIPTION` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL|`DESCRIPTION` varchar(4000) DEFAULT NULL| |SERDES|SERIALIZER_CLASS|`SERIALIZER_CLASS` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL|`SERIALIZER_CLASS` varchar(4000) DEFAULT NULL| There are few more... was: ||Table||Column||Fresh Install||Upgrade case|| |PARTITION_EVENTS|CAT_NAME|`CAT_NAME` varchar(256) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL|`CAT_NAME` varchar(256) DEFAULT NULL| |SERDES|DESCRIPTION|`DESCRIPTION` varchar(4000) DEFAULT NULL|`DESCRIPTION` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL| |SERDES|SERIALIZER_CLASS|`SERIALIZER_CLASS` varchar(4000) DEFAULT NULL|`SERIALIZER_CLASS` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL| There are few more... > Char set for few columns in HMS schema for fresh install and upgrade case > are not in sync > --- > > Key: HIVE-27588 > URL: https://issues.apache.org/jira/browse/HIVE-27588 > Project: Hive > Issue Type: Bug >Reporter: Pravin Sinha >Assignee: Pravin Sinha >Priority: Major > > > ||Table||Column||Fresh Install||Upgrade case|| > |PARTITION_EVENTS|CAT_NAME|`CAT_NAME` varchar(256) CHARACTER SET latin1 > COLLATE latin1_bin DEFAULT NULL|`CAT_NAME` varchar(256) DEFAULT NULL| > |SERDES|DESCRIPTION|`DESCRIPTION` varchar(4000) CHARACTER SET latin1 COLLATE > latin1_bin DEFAULT NULL|`DESCRIPTION` varchar(4000) DEFAULT NULL| > |SERDES|SERIALIZER_CLASS|`SERIALIZER_CLASS` varchar(4000) CHARACTER SET > latin1 COLLATE latin1_bin DEFAULT NULL|`SERIALIZER_CLASS` varchar(4000) > DEFAULT NULL| > There are few more... > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27588) Char set for few columns in HMS schema for fresh install and upgrade case are not in sync
[ https://issues.apache.org/jira/browse/HIVE-27588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pravin Sinha updated HIVE-27588: Summary: Char set for few columns in HMS schema for fresh install and upgrade case are not in sync (was: Char set for few columns in HMS schema for fresh install and upgrade case is not in sync) > Char set for few columns in HMS schema for fresh install and upgrade case > are not in sync > --- > > Key: HIVE-27588 > URL: https://issues.apache.org/jira/browse/HIVE-27588 > Project: Hive > Issue Type: Bug >Reporter: Pravin Sinha >Assignee: Pravin Sinha >Priority: Major > > > ||Table||Column||Fresh Install||Upgrade case|| > |PARTITION_EVENTS|CAT_NAME|`CAT_NAME` varchar(256) CHARACTER SET latin1 > COLLATE latin1_bin DEFAULT NULL|`CAT_NAME` varchar(256) DEFAULT NULL| > |SERDES|DESCRIPTION|`DESCRIPTION` varchar(4000) DEFAULT NULL|`DESCRIPTION` > varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL| > |SERDES|SERIALIZER_CLASS|`SERIALIZER_CLASS` varchar(4000) DEFAULT > NULL|`SERIALIZER_CLASS` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin > DEFAULT NULL| > There are few more... > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27588) Char set for few columns in HMS schema for fresh install and upgrade case is not in sync
[ https://issues.apache.org/jira/browse/HIVE-27588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pravin Sinha updated HIVE-27588: Description: ||Table||Column||Fresh Install||Upgrade case|| |PARTITION_EVENTS|CAT_NAME|`CAT_NAME` varchar(256) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL|`CAT_NAME` varchar(256) DEFAULT NULL| |SERDES|DESCRIPTION|`DESCRIPTION` varchar(4000) DEFAULT NULL|`DESCRIPTION` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL| |SERDES|SERIALIZER_CLASS|`SERIALIZER_CLASS` varchar(4000) DEFAULT NULL|`SERIALIZER_CLASS` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL| There are few more... > Char set for few columns in HMS schema for fresh install and upgrade case > is not in sync > -- > > Key: HIVE-27588 > URL: https://issues.apache.org/jira/browse/HIVE-27588 > Project: Hive > Issue Type: Bug >Reporter: Pravin Sinha >Assignee: Pravin Sinha >Priority: Major > > > ||Table||Column||Fresh Install||Upgrade case|| > |PARTITION_EVENTS|CAT_NAME|`CAT_NAME` varchar(256) CHARACTER SET latin1 > COLLATE latin1_bin DEFAULT NULL|`CAT_NAME` varchar(256) DEFAULT NULL| > |SERDES|DESCRIPTION|`DESCRIPTION` varchar(4000) DEFAULT NULL|`DESCRIPTION` > varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL| > |SERDES|SERIALIZER_CLASS|`SERIALIZER_CLASS` varchar(4000) DEFAULT > NULL|`SERIALIZER_CLASS` varchar(4000) CHARACTER SET latin1 COLLATE latin1_bin > DEFAULT NULL| > There are few more... > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27588) Char set for few columns in HMS schema for fresh install and upgrade case is not in sync
[ https://issues.apache.org/jira/browse/HIVE-27588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pravin Sinha updated HIVE-27588: Summary: Char set for few columns in HMS schema for fresh install and upgrade case is not in sync (was: Char set for few columns in HMS schema for fresh install and upgrade case in not in sync) > Char set for few columns in HMS schema for fresh install and upgrade case > is not in sync > -- > > Key: HIVE-27588 > URL: https://issues.apache.org/jira/browse/HIVE-27588 > Project: Hive > Issue Type: Bug >Reporter: Pravin Sinha >Assignee: Pravin Sinha >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27588) Char set for few columns in HMS schema for fresh install and upgrade case in not in sync
Pravin Sinha created HIVE-27588: --- Summary: Char set for few columns in HMS schema for fresh install and upgrade case in not in sync Key: HIVE-27588 URL: https://issues.apache.org/jira/browse/HIVE-27588 Project: Hive Issue Type: Bug Reporter: Pravin Sinha Assignee: Pravin Sinha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27525) Ease the write permissions on external table during create table operation
[ https://issues.apache.org/jira/browse/HIVE-27525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riju Trivedi updated HIVE-27525: Description: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. CTAS query with location specified is expected to fail at runtime (trying to create staging directory under table location) without WRITE permissions. was: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. CTAS query with location specified is expected to fail at runtime without , trying to create staging directory under table location. > Ease the write permissions on external table during create table operation > -- > > Key: HIVE-27525 > URL: https://issues.apache.org/jira/browse/HIVE-27525 > Project: Hive > Issue Type: Improvement > Components: Standalone Metastore >Reporter: Sai Hemanth Gantasala >Assignee: Riju Trivedi >Priority: Major > Labels: pull-request-available > > During the creation of external tables with a specified location, the general > expectation is that the data is already present or the data might be > externally added to the location without involving HMS. So, it is really not > required to have read and write permissions on an external table during the > creation time. > This enhancement can address security concerns where currently the users had > to be granted unnecessary write permissions on an external file location when > the table is only used for reading the data. > Update/delete operations would anyway require write permissions. > CTAS query with location specified is expected to fail at runtime (trying to > create staging directory under table location) without WRITE permissions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27525) Ease the write permissions on external table during create table operation
[ https://issues.apache.org/jira/browse/HIVE-27525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riju Trivedi updated HIVE-27525: Description: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. CTAS query with location specified is expected to fail at runtime without , trying to create staging directory under table location. was: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. In case of CTAS with location specified, query would pass he authorization > Ease the write permissions on external table during create table operation > -- > > Key: HIVE-27525 > URL: https://issues.apache.org/jira/browse/HIVE-27525 > Project: Hive > Issue Type: Improvement > Components: Standalone Metastore >Reporter: Sai Hemanth Gantasala >Assignee: Riju Trivedi >Priority: Major > Labels: pull-request-available > > During the creation of external tables with a specified location, the general > expectation is that the data is already present or the data might be > externally added to the location without involving HMS. So, it is really not > required to have read and write permissions on an external table during the > creation time. > This enhancement can address security concerns where currently the users had > to be granted unnecessary write permissions on an external file location when > the table is only used for reading the data. > Update/delete operations would anyway require write permissions. > CTAS query with location specified is expected to fail at runtime without , > trying to create staging directory under table location. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27525) Ease the write permissions on external table during create table operation
[ https://issues.apache.org/jira/browse/HIVE-27525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riju Trivedi updated HIVE-27525: Description: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. In case of CTAS with location specified, query would pass he authorization was: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. In case of CTAS with location specificed > Ease the write permissions on external table during create table operation > -- > > Key: HIVE-27525 > URL: https://issues.apache.org/jira/browse/HIVE-27525 > Project: Hive > Issue Type: Improvement > Components: Standalone Metastore >Reporter: Sai Hemanth Gantasala >Assignee: Riju Trivedi >Priority: Major > Labels: pull-request-available > > During the creation of external tables with a specified location, the general > expectation is that the data is already present or the data might be > externally added to the location without involving HMS. So, it is really not > required to have read and write permissions on an external table during the > creation time. > This enhancement can address security concerns where currently the users had > to be granted unnecessary write permissions on an external file location when > the table is only used for reading the data. > Update/delete operations would anyway require write permissions. > In case of CTAS with location specified, query would pass he authorization -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27525) Ease the write permissions on external table during create table operation
[ https://issues.apache.org/jira/browse/HIVE-27525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riju Trivedi updated HIVE-27525: Description: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. In case of CTAS with location specificed was: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. > Ease the write permissions on external table during create table operation > -- > > Key: HIVE-27525 > URL: https://issues.apache.org/jira/browse/HIVE-27525 > Project: Hive > Issue Type: Improvement > Components: Standalone Metastore >Reporter: Sai Hemanth Gantasala >Assignee: Riju Trivedi >Priority: Major > Labels: pull-request-available > > During the creation of external tables with a specified location, the general > expectation is that the data is already present or the data might be > externally added to the location without involving HMS. So, it is really not > required to have read and write permissions on an external table during the > creation time. > This enhancement can address security concerns where currently the users had > to be granted unnecessary write permissions on an external file location when > the table is only used for reading the data. > Update/delete operations would anyway require write permissions. > In case of CTAS with location specificed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27525) Ease the write permissions on external table during create table operation
[ https://issues.apache.org/jira/browse/HIVE-27525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-27525: -- Labels: pull-request-available (was: ) > Ease the write permissions on external table during create table operation > -- > > Key: HIVE-27525 > URL: https://issues.apache.org/jira/browse/HIVE-27525 > Project: Hive > Issue Type: Improvement > Components: Standalone Metastore >Reporter: Sai Hemanth Gantasala >Assignee: Riju Trivedi >Priority: Major > Labels: pull-request-available > > During the creation of external tables with a specified location, the general > expectation is that the data is already present or the data might be > externally added to the location without involving HMS. So, it is really not > required to have read and write permissions on an external table during the > creation time. > This enhancement can address security concerns where currently the users had > to be granted unnecessary write permissions on an external file location when > the table is only used for reading the data. > Update/delete operations would anyway require write permissions. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HIVE-27525) Ease the write permissions on external table during create table operation
[ https://issues.apache.org/jira/browse/HIVE-27525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riju Trivedi updated HIVE-27525: Description: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be granted unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. was: During the creation of external tables with a specified location, the general expectation is that the data is already present or the data might be externally added to the location without involving HMS. So, it is really not required to have read and write permissions on an external table during the creation time. This enhancement can address security concerns where currently the users had to be grant unnecessary write permissions on an external file location when the table is only used for reading the data. Update/delete operations would anyway require write permissions. > Ease the write permissions on external table during create table operation > -- > > Key: HIVE-27525 > URL: https://issues.apache.org/jira/browse/HIVE-27525 > Project: Hive > Issue Type: Improvement > Components: Standalone Metastore >Reporter: Sai Hemanth Gantasala >Assignee: Riju Trivedi >Priority: Major > > During the creation of external tables with a specified location, the general > expectation is that the data is already present or the data might be > externally added to the location without involving HMS. So, it is really not > required to have read and write permissions on an external table during the > creation time. > This enhancement can address security concerns where currently the users had > to be granted unnecessary write permissions on an external file location when > the table is only used for reading the data. > Update/delete operations would anyway require write permissions. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27587) Add TIME data type
okumin created HIVE-27587: - Summary: Add TIME data type Key: HIVE-27587 URL: https://issues.apache.org/jira/browse/HIVE-27587 Project: Hive Issue Type: New Feature Components: Metastore, Query Processor Affects Versions: 4.0.0-alpha-2 Reporter: okumin Assignee: okumin Support the TIME type defined in the SQL standard -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HIVE-27586) Parse dates from strings ignoring trailing (potentialy) invalid chars
Stamatis Zampetakis created HIVE-27586: -- Summary: Parse dates from strings ignoring trailing (potentialy) invalid chars Key: HIVE-27586 URL: https://issues.apache.org/jira/browse/HIVE-27586 Project: Hive Issue Type: Improvement Components: HiveServer2 Affects Versions: 4.0.0-beta-1 Reporter: Stamatis Zampetakis Assignee: Stamatis Zampetakis The goal of this ticket is to extract and return a valid date from a string value when there is a valid date prefix in the string. The following table contains a few illustrative examples highlighting what happens now and what will happen after the proposed changes to ignore trailing characters. HIVE-20007 introduced some behavior changes around this area so the table also displays what was the Hive behavior before that change. ||ID||String value||Before HIVE-20007||Current behavior||Ignore trailing chars|| |1|2023-08-03_16:02:00|2023-08-03|null|2023-08-03| |2|2023-08-03-16:02:00|2023-08-03|null|2023-08-03| |3|2023-08-0316:02:00|2024-06-11|null|2023-08-03| |4|03-08-2023|0009-02-12|null|0003-08-20| |5|2023-08-03 GARBAGE|2023-08-03|2023-08-03|2023-08-03| |6|2023-08-03TGARBAGE|2023-08-03|2023-08-03|2023-08-03| |7|2023-08-03_GARBAGE|2023-08-03|null|2023-08-03| This change partially (see example 3 and 4) restores the behavior changes introduced by HIVE-20007 and at the same time makes the current behavior of handling trailing invalid chars more uniform. This change will have an impact on various Hive SQL functions and operators (+/-) that accept dates from string values. A partial list of affected functions is outlined below: * CAST (V AS DATE) * CAST (V AS TIMESTAMP) * TO_DATE * DATE_ADD * DATE_DIFF * WEEKOFYEAR * DAYOFWEEK * TRUNC -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-27578) Refactor genJoinRelNode to use genAllRexNode instead of genAllExprNodeDesc
[
https://issues.apache.org/jira/browse/HIVE-27578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752333#comment-17752333
]
Stamatis Zampetakis commented on HIVE-27578:
[~soumyakanti.das] I don't understand the motivation and the impact of this
change. Can you please elaborate a bit more on the description? If you can
include some examples or tests that would be great as well.
> Refactor genJoinRelNode to use genAllRexNode instead of genAllExprNodeDesc
> --
>
> Key: HIVE-27578
> URL: https://issues.apache.org/jira/browse/HIVE-27578
> Project: Hive
> Issue Type: Improvement
>Reporter: Soumyakanti Das
>Assignee: Soumyakanti Das
>Priority: Major
> Labels: pull-request-available
>
> Currently {{genJoinRelNode}} method relies on {{genAllExprNodeDesc}} for
> adding backticks to the ON clause, but we can use {{genAllRexNode}} method
> instead, which is better because we already use RexNodes in the method and
> this change will make it depend on only RexNodes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
