[
https://issues.apache.org/jira/browse/PHOENIX-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1661:
----------------------------------
Description:
Take a look at the JSON built-in functions that are implemented in Postgres
(http://www.postgresql.org/docs/9.3/static/functions-json.html) and implement
the same for Phoenix in Java following this guide:
http://phoenix-hbase.blogspot.com/2013/04/how-to-add-your-own-built-in-function.html
Examples of functions include ARRAY_TO_JSON, ROW_TO_JSON, TO_JSON, etc. The
implementation of these built-in functions will be impacted by how JSON is
stored in Phoenix. See PHOENIX-628. An initial implementation could work off of
a simple text-based JSON representation and then when a native JSON type is
implemented, they could be reworked to be more efficient.
was:
Take a look at the typical math functions that are implemented in relational
database systems
(http://www.postgresql.org/docs/current/static/functions-math.html) and
implement the same for Phoenix in Java following this guide:
http://phoenix-hbase.blogspot.com/2013/04/how-to-add-your-own-built-in-function.html
Examples of missing functions include POWER, LOG, EXP, SQRT, CBRT, etc. As a
guide, examine how ROUND is implemented in Phoenix as an abstract function with
concrete functions per type: long, decimal, and date/time types.
> Implement built-in functions for JSON
> -------------------------------------
>
> Key: PHOENIX-1661
> URL: https://issues.apache.org/jira/browse/PHOENIX-1661
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Labels: gsoc2015
>
> Take a look at the JSON built-in functions that are implemented in Postgres
> (http://www.postgresql.org/docs/9.3/static/functions-json.html) and implement
> the same for Phoenix in Java following this guide:
> http://phoenix-hbase.blogspot.com/2013/04/how-to-add-your-own-built-in-function.html
> Examples of functions include ARRAY_TO_JSON, ROW_TO_JSON, TO_JSON, etc. The
> implementation of these built-in functions will be impacted by how JSON is
> stored in Phoenix. See PHOENIX-628. An initial implementation could work off
> of a simple text-based JSON representation and then when a native JSON type
> is implemented, they could be reworked to be more efficient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
