hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tzolov <...@git.apache.org>
Subject [GitHub] incubator-hawq pull request: HAWQ-178: Add JSON plugin support in ...
Date Sat, 30 Jan 2016 15:11:29 GMT
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`? 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message