[jira] [Updated] (HIVE-21256) Vectorized LENGTH UDF doesn't respect the max length of VARCHAR or CHAR in Hive 2

2019-02-13 Thread Teddy Choi (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Teddy Choi updated HIVE-21256:
--
Status: Patch Available  (was: Open)

> Vectorized LENGTH UDF doesn't respect the max length of VARCHAR or CHAR in 
> Hive 2
> -
>
> Key: HIVE-21256
> URL: https://issues.apache.org/jira/browse/HIVE-21256
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 2.3.4
>Reporter: Teddy Choi
>Assignee: Teddy Choi
>Priority: Major
> Attachments: HIVE-21256.2.branch-2.patch
>
>
> After HIVE-19951 is fixed, there still are some cases that vectorized length 
> UDF doesn't respect the max length of VARCHAR or CHAR. StringLength has an 
> internal bug. Moreover, it's hard to get input data type details in Hive 2, 
> unlike Hive 3. So separate both implementation to keep code clean in Hive 3 
> while the changes minimal in Hive 2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21256) Vectorized LENGTH UDF doesn't respect the max length of VARCHAR or CHAR in Hive 2

2019-02-13 Thread Teddy Choi (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Teddy Choi updated HIVE-21256:
--
Attachment: HIVE-21256.2.branch-2.patch

> Vectorized LENGTH UDF doesn't respect the max length of VARCHAR or CHAR in 
> Hive 2
> -
>
> Key: HIVE-21256
> URL: https://issues.apache.org/jira/browse/HIVE-21256
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 2.3.4
>Reporter: Teddy Choi
>Assignee: Teddy Choi
>Priority: Major
> Attachments: HIVE-21256.2.branch-2.patch
>
>
> After HIVE-19951 is fixed, there still are some cases that vectorized length 
> UDF doesn't respect the max length of VARCHAR or CHAR. StringLength has an 
> internal bug. Moreover, it's hard to get input data type details in Hive 2, 
> unlike Hive 3. So separate both implementation to keep code clean in Hive 3 
> while the changes minimal in Hive 2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)