[
https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878816#action_12878816
]
Edward Capriolo commented on HIVE-1135:
---------------------------------------
FMI. What is the hbase review board?
> Stash this stuff under docs/ instead of creating another top level directory
> (xdocs/)
It seems like xdocs is convention, also did not want to step on whatever is in
docs. I will see if they both can live in docs happily.
>JDOM ivy.
Right now most/all the stuff in /lib comes from ivy. We should open up a
another ticket and convert the entire project to ivy.
>velocity.log
Yes my local version (next patch already fixes that)
> * Limit the initial import to the convents of the Hive Language Manual. I
> think some things should actually stay on the wiki, but the language manual
> is definitely one of those things that we want to have in VCS.
I agree the initial import should come from the Hive Language Manual only. To
me wiki just screems, "I did not have time to write a full complete doc."
Generalization coming: 99% of the things in the wiki should be in xdocs. Users
only want one place for authoritative information. Wikis and xdoc will fall out
of sync, confusion follows.
> Move hive language manual and all wiki based documentation to forest
> --------------------------------------------------------------------
>
> Key: HIVE-1135
> URL: https://issues.apache.org/jira/browse/HIVE-1135
> Project: Hadoop Hive
> Issue Type: Task
> Components: Documentation
> Affects Versions: 0.5.0
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Fix For: 0.6.0
>
> Attachments: hive-1335-1.patch.txt, hive-1335-2.patch.txt,
> jdom-1.1.jar
>
>
> Currently the Hive Language Manual and many other critical pieces of
> documentation are on the Hive wiki.
> Right now we count on the author of a patch to follow up and add wiki
> entries. While we do a decent job with this, new features can be missed. Or
> using running older/newer branches can not locate relevant documentation for
> their branch.
> ..example of a perception I do not think we want to give off...
> http://dev.hubspot.com/bid/30170/Who-Loves-the-Magic-Undocumented-Hive-Mapjoin-This-Guy
> We should generate our documentation in the way hadoop & hbase does, inline
> using forest. I would like to take the lead on this, but we need a lot of
> consensus on doing this properly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
