You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2020/03/30 21:25:00 UTC
[jira] [Updated] (IMPALA-9576) Add built-in function for BINARY
columns
[ https://issues.apache.org/jira/browse/IMPALA-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Csaba Ringhofer updated IMPALA-9576:
------------------------------------
Description:
Hive supports a few built-in functions for BINARY columns according to
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF
Already supported in Impala for STRING:
- hex, unhex
- concat
- decode, encode
- substr/substring
Currently not supported in Impala for STRING:
- base64, unbase64
- binary (a special casting syntax just for BINARY)
- md5, sha, sha1, sha2, crc32
- aes_encrypt/aes_decrypt
At the first glance I think that what we should implement in Impala is:
- all the functions that already work for STRING
- base64, unbase64 (needed for text files anyway)
- binary() - may worth adding to get closer to Hive SQL, but can cause problems as the name is the same as a keyword
was:
Hive supports a few built-in functions for BINARY columns according to
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF
Already supported in Impala for STRING:
- length (the Hive wiki doesn't mention it but it works)
- hex, unhex
- concat
- decode, encode
- substr/substring
Currently not supported in Impala for STRING:
- base64, unbase64
- binary (a special casting syntax just for BINARY)
- md5, sha, sha1, sha2, crc32
- aes_encrypt/aes_decrypt
At the first glance I think that what we should implement in Impala is:
- all the functions that already work for STRING
- base64, unbase64 (needed for text files anyway)
- binary() - may worth adding to get closer to Hive SQL, but can cause problems as the name is the same as a keyword
> Add built-in function for BINARY columns
> ----------------------------------------
>
> Key: IMPALA-9576
> URL: https://issues.apache.org/jira/browse/IMPALA-9576
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Csaba Ringhofer
> Priority: Major
>
> Hive supports a few built-in functions for BINARY columns according to
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF
> Already supported in Impala for STRING:
> - hex, unhex
> - concat
> - decode, encode
> - substr/substring
> Currently not supported in Impala for STRING:
> - base64, unbase64
> - binary (a special casting syntax just for BINARY)
> - md5, sha, sha1, sha2, crc32
> - aes_encrypt/aes_decrypt
> At the first glance I think that what we should implement in Impala is:
> - all the functions that already work for STRING
> - base64, unbase64 (needed for text files anyway)
> - binary() - may worth adding to get closer to Hive SQL, but can cause problems as the name is the same as a keyword
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org