[
https://issues.apache.org/jira/browse/HAWQ-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858234#comment-15858234
]
ASF GitHub Bot commented on HAWQ-1304:
--------------------------------------
Github user lisakowen commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/94#discussion_r100115473
--- Diff: markdown/pxf/ReadWritePXF.html.md.erb ---
@@ -131,6 +149,8 @@ Note: The <code class="ph codeph">DELIMITER</code>
parameter is mandatory.
</tbody>
</table>
+**Notes**: Metadata identifies the Java class that provides field
definitions in the relation. OutputFormat identifies the file format for which
a specific profile is optimized. While the built-in `Hive*` profiles provide
Metadata and OutputFormat classes, most profiles will have no need to implement
or specify these classes.
--- End diff --
the statement is kind of vague, yes. i will make it clearer.
it seems to me that the outputFormat property is more admin- or
developer-focused. what i mean here is that a typical end-user using a Hive*
profile probably does not need to know about the setting. an admin configuring
custom profiles or a developer creating a custom plug-in may be interested.
the current admin- and developer- focused PXF docs need some attention. can we
address a more detailed discussion of this property as part of that rework at a
later time?
> documentation changes for HAWQ-1228
> -----------------------------------
>
> Key: HAWQ-1304
> URL: https://issues.apache.org/jira/browse/HAWQ-1304
> Project: Apache HAWQ
> Issue Type: New Feature
> Components: Documentation
> Affects Versions: 2.1.0.0-incubating
> Reporter: Lisa Owen
> Assignee: David Yozie
> Priority: Minor
>
> - new pxf-profiles.xml outputFormat parameter
> - hive table access via external table and hcatalog now uses optimal profile
> for each fragment
> - others
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
