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

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

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

    https://github.com/apache/incubator-hawq-docs/pull/126#discussion_r124423088
  
    --- Diff: markdown/pxf/HivePXF.html.md.erb ---
    @@ -495,9 +500,16 @@ Use the `HiveORC` profile to access ORC format data. 
The `HiveORC` profile provi
         - `=`, `>`, `<`, `>=`, `<=`, `IS NULL`, and `IS NOT NULL` operators 
and comparisons between the `float8` and `float4` types
         - `IN` operator on arrays of `int2`, `int4`, `int8`, `boolean`, and 
`text`
     
    -- Complex type support - You can access Hive tables composed of array, 
map, struct, and union data types. PXF serializes each of these complex types 
to `text`.
    +When choosing an ORC-supporting profile, consider the following:
    +
    +- The `HiveORC` profile supports complex types. You can access Hive tables 
composed of array, map, struct, and union data types. PXF serializes each of 
these complex types to `text`.  
    +
    +    The `HiveVectorizedORC` profile does not support complex types.
    +
    +- The `HiveVectorizedORC` profile reads 1024 rows of data, while the 
`HiveORC` profile reads only a single row at a time.
    --- End diff --
    
    profile reads 1024 rows of data at once


> docs - add usage info for HiveVectorizedORC profile
> ---------------------------------------------------
>
>                 Key: HAWQ-1491
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1491
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Lisa Owen
>            Assignee: David Yozie
>
> add usage info and an example for the new HiveVectorizedORC profile to the 
> Hive plug-in page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to