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

renmin commented on PHOENIX-1661:
---------------------------------

HI,
   My name is renmin.liu, i am persuing my master degree in Peking university, 
My major is software engineering. I am interested in this function and eager to 
join this project. I have more than 3 years java work experience before backing 
to university again, I was familiar with json and used HBase in one project. 
But I have never taken part in open source project before. So hoping get your 
more help.
   I have gone through the description, I know that the main purpose is 
implementing translating between json and other data format or type. I used to 
use apache GSON API in many projects, i want to know the difference of the way 
of implementing from GSON, and could it refer to GSON's source code. Perhaps it 
lies in storage layer. in addition, could you tell me detailed steps i shoud do 
next? 
thanks james~

> 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)

Reply via email to