[
https://issues.apache.org/jira/browse/HIVE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652462#action_12652462
]
Ashish Thusoo commented on HIVE-81:
-----------------------------------
I know that all the subprojects are doing this and the convention is to checkin
the generated file, but I do think it makes more sense not to do that and just
generate the code when the publish target is called. I am not sure that there
are any significant advantages of checking in generated code but there seem to
be a lot of disadvantages. This is also something that is being discussed in
the larger hadoop context. The thread where this is being discussed is as
follows:
http://mail-archives.apache.org/mod_mbox/hadoop-core-dev/200812.mbox/browser
Clearly even there the preference is not to check in the generated docs.
> Make forrest docs for Hive web site along the lines of
> http://hadoop.apache.org/core/
> -------------------------------------------------------------------------------------
>
> Key: HIVE-81
> URL: https://issues.apache.org/jira/browse/HIVE-81
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Documentation
> Reporter: Jeff Hammerbacher
> Attachments: favicon.ico, hadoop-logo.jpg, HIVE-81.patch,
> hive_small.jpg
>
>
> Hive should ship with documentation, like Hadoop, instead of using the wiki
> as the official documentation repository. To get there, we'll need a set of
> xml files to grind through forrest, if we want to reuse the same mechanisms
> as the other sites.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
