[
https://issues.apache.org/jira/browse/PHOENIX-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625810#comment-14625810
]
ASF GitHub Bot commented on PHOENIX-1661:
-----------------------------------------
GitHub user petercdc opened a pull request:
https://github.com/apache/phoenix/pull/101
PHOENIX-1661 Implement built-in functions for JSON
1.Adding following JSON operators:
JSON get data Operator : "->" "->>" "#>" "#>>"
JSON Boolean Operactor : "?" "?|" "?&" "<@" "@>"
2.add a unit test file: JSONOperationT.java
3.Adding functions for some JSON operators in PhoenixJson.java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/petercdc/phoenix jsoncdc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/101.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #101
----
commit a131aa3664d18a048a41b0dab9155d90b17103f5
Author: LiChiachi <[email protected]>
Date: 2015-07-01T10:55:39Z
rebase from json brance (but just recreate new branch base on json
branch)
fixed:
All ParseNode and Visiter , All ExpressionVisiter , PhoenixJson method
to be used for Expression method
Not fixed yet:
Expression method exclusive JsonPonit Operator
commit 8babfb5fba20d24a1c65b02fdd13075b0632d4fc
Author: LiChiachi <[email protected]>
Date: 2015-07-02T08:48:36Z
rebase on json branch (but create new branch base on json branch)
fixed:
All ParseNode and All ExpressionNode exclusive Superset and Subset
not fixed yet:
Type Checking for As Element Node , Superset and Subset Node
commit 077d5f41da0c22bcafd9387df90c60ea0be659ed
Author: LiChiachi <[email protected]>
Date: 2015-07-06T09:56:47Z
rebase on json branch (but recreate new branch based on json branch)
fixed:
All ParseNode and ExpressionNode are done
not fixed yet:
TypeChecking for Skipping checking type on JsongetElementExpression
commit 5b8a43e09202b04e3371ff8cfd8451b68baa2759
Author: LiChiachi <[email protected]>
Date: 2015-07-10T01:52:53Z
rebase on json branch (but recreate new branch based on json branch)
fix bug wronging with superset and subset node
commit 7793e94cf27d4057b633b7c67234f6e451d5577c
Author: Andy <[email protected]>
Date: 2015-07-11T09:37:09Z
First Version
commit 229939099154042af98b24839cfb483624400fb0
Author: Andy <[email protected]>
Date: 2015-07-11T11:15:14Z
fix type checking bug
commit ff7e9edd126b65796a41d5bf8e567d50729e3989
Author: Andy <[email protected]>
Date: 2015-07-11T14:30:56Z
add Apache license
commit fd4604cbb799600a87da0647671e8dbad6a8c6a7
Author: Andy <[email protected]>
Date: 2015-07-13T12:22:08Z
fix some expressions bugs
----
> 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)
