[
https://issues.apache.org/jira/browse/PHOENIX-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382705#comment-14382705
]
James Taylor commented on PHOENIX-1661:
---------------------------------------
[~saloni_udani] - you'll find lots of documentation on our website:
http://phoenix.apache.org/. Data type info is link there to here:
http://phoenix.apache.org/language/datatypes.html. In the code, see PDataType
and its subclasses.
I don't think starting with the attempt to implement a native json datatype
would be a good way to go. I also don't think there's enough time in the GSoC
program to implement it. We're also pretty busy on some other sizable
initiatives, so you may not get enough help. Maybe best to take a look at some
other JIRAs that would ease you into Phoenix and come back to this later?
> 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: JSON, Java, SQL, gsoc2015, mentor
> Attachments: 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.3.4#6332)
