phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DanielSun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1661) Implement built-in functions for JSON
Date Thu, 21 Dec 2017 13:45:06 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300037#comment-16300037
] 

DanielSun commented on PHOENIX-1661:
------------------------------------

We are very interested in this issue, and try to provide an idea, the following is our implement
document. 
We are trying to write the program accroding to this document.
[^Implement built-in functions for JSON.pdf]

> Implement built-in functions for JSON
> -------------------------------------
>
>                 Key: PHOENIX-1661
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1661
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: LeiWang
>              Labels: JSON, Java, SQL, gsoc2015, mentor
>         Attachments: Implement built-in functions for JSON.pdf, PHOENIX-1661.patch, PhoenixJSONSpecification-First-Draft.pdf
>
>
> 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.4.14#64029)

Mime
View raw message