[
https://issues.apache.org/jira/browse/PHOENIX-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Buzsaki updated PHOENIX-1055:
----------------------------------
Attachment: PHOENIX-1055_2.patch
I'm working on integrating the ENCODE built-in and the new built-in functions
and have come across a bit of an issue with existing integration tests in
EncodeFunctionIT. Attached is my WIP patch.
It turns out that phoenix doesn't currently support encoding to HEX, it only
supports decoding from it. In fact, HEX is used in the unit tests as an example
of an unsupported format. See here:
https://github.com/apache/phoenix/blob/master/phoenix-core/src/it/java/org/apache/phoenix/end2end/EncodeFunctionIT.java#L135
With my work to integrate the two, I've moved the encoding logic to the
EncodeFormat#encode(String) member method of EncodeFormat. Because of this,
every EncodeFormat is required to provide an encode implementation and it is
impossible for there to be an unsupported format.
Thoughts on how to proceed here?
> Add support for the built-in functions HEX, OCT, and BIN
> ---------------------------------------------------------
>
> Key: PHOENIX-1055
> URL: https://issues.apache.org/jira/browse/PHOENIX-1055
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Kyle Buzsaki
> Attachments: PHOENIX-1055.patch, PHOENIX-1055_2.patch
>
>
> Add built-in functions to produce hexadecimal, octal, and binary string
> representations of numeric values.
> Example Function Specification:
> http://dev.mysql.com/doc/refman/5.0/en/string-functions.html#function_hex
> http://dev.mysql.com/doc/refman/5.0/en/string-functions.html#function_oct
> http://dev.mysql.com/doc/refman/5.0/en/string-functions.html#function_bin
--
This message was sent by Atlassian JIRA
(v6.2#6252)
