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

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_r51346000
  
    --- Diff: pxf/pxf-service/src/main/resources/pxf-profiles-default.xml ---
    @@ -128,4 +128,26 @@ 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>
    +           <plugins>
    +                   
<fragmenter>org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter</fragmenter>
    +                   
<accessor>org.apache.hawq.pxf.plugins.json.JsonAccessor</accessor>
    +                   
<resolver>org.apache.hawq.pxf.plugins.json.JsonResolver</resolver>
    +           </plugins>
    +   </profile>
    +   <profile>
    +           <name>JSON-PP</name>
    --- End diff --
    
    JSON-PP differs from JSON only by the hard coded property 
`onerecordperline=false`.  
    I will remove it though in favor of JSON + explicit parameter in the DDL 
definition.
    About the name shall i change it from `JSON` to `Json`? 



> 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: Goden Yao
>             Fix For: backlog
>
>         Attachments: PXFJSONPluginforHAWQ2.0andPXF3.0.0.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