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

ASF GitHub Bot commented on HAWQ-178:
-------------------------------------

Github user tzolov commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq/pull/302#discussion_r52080654
  
    --- Diff: pxf/pxf-service/src/main/resources/pxf-profiles-default.xml ---
    @@ -128,4 +128,13 @@ under the License.
                 
<resolver>org.apache.hawq.pxf.plugins.gemfirexd.GemFireXDResolver</resolver>
             </plugins>
         </profile>
    +    <profile>
    +        <name>Json</name>
    +        <description>A profile for JSON data, one JSON record per 
line</description>
    --- End diff --
    
    Thanks for spotting this @GodenYao! Just fixed it
    
    P.S. as an experiment i've implemented a Json Resolver that leverages 
[JsonPath](https://github.com/jayway/JsonPath). It allows you to  traverse 
arbitrary complex json records. (current expression mechanism is quite 
limited). But this an experimental work and we should leave a possible future 
improvement. Perhaps as an additional 3rd mode -  the most flexible but 
potentially slowest. 


> Add JSON plugin support in code base
> ------------------------------------
>
>                 Key: HAWQ-178
>                 URL: https://issues.apache.org/jira/browse/HAWQ-178
>             Project: Apache HAWQ
>          Issue Type: New Feature
>          Components: PXF
>            Reporter: Goden Yao
>            Assignee: Christian Tzolov
>             Fix For: backlog
>
>         Attachments: PXFJSONPluginforHAWQ2.0andPXF3.0.0.pdf, 
> PXFJSONPluginforHAWQ2.0andPXF3.0.0v.2.pdf, 
> PXFJSONPluginforHAWQ2.0andPXF3.0.0v.3.pdf
>
>
> JSON has been a popular format used in HDFS as well as in the community, 
> there has been a few JSON PXF plugins developed by the community and we'd 
> like to see it being incorporated into the code base as an optional package.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to