You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2010/02/05 18:39:28 UTC
[jira] Created: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
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
Reporter: Edward Capriolo
Assignee: Edward Capriolo
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.
[jira] Commented: (HIVE-1135) Move hive language manual and
tutorial to version control
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879603#action_12879603 ]
Carl Steinbach commented on HIVE-1135:
--------------------------------------
I'm +1 on committing this (either Ed's last patch, or the one I just added that contains three very small tweaks).
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE
>
>
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878792#action_12878792 ]
HBase Review Board commented on HIVE-1135:
------------------------------------------
Message from: "Carl Steinbach" <ca...@cloudera.com>
bq. On 2010-06-14 15:26:25, Carl Steinbach wrote:
bq. > Looks good overall.
bq. >
bq. > A couple suggestions:
bq. > * Stash this stuff under docs/ instead of creating another top level directory (xdocs/)
bq. > * Manage the jdom dependency with Ivy.
bq. > * 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.
* Running the docs target causes a 'velocity.log' file to appear in the source root directory. This should probably be redirected to build/dist/docs. See http://velocity.apache.org/engine/releases/velocity-1.4/developer-guide.html#Velocity Configuration Keys and Values
- Carl
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.hbase.org/r/178/#review217
-----------------------------------------------------------
> 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "John Sichi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883376#action_12883376 ]
John Sichi commented on HIVE-1135:
----------------------------------
Just a note: when supplying patches (whether from svn or git), make sure they can be applied with
patch -p0 < hive-1135.?.patch
For this one, I had to use patch -p1.
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and tutorial
to version control
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Summary: Move hive language manual and tutorial to version control (was: Move hive language manual and all wiki based documentation to forest)
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Summary: Use Anakia for version controlled documentation (was: Move hive language manual and tutorial to version control)
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE
>
>
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878759#action_12878759 ]
HBase Review Board commented on HIVE-1135:
------------------------------------------
Message from: "Carl Steinbach" <ca...@cloudera.com>
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.hbase.org/r/178/
-----------------------------------------------------------
Review request for Hive Developers.
Summary
-------
Submitted on behalf of Ed Capriolo.
This addresses bug hive-1135.
http://issues.apache.org/jira/browse/hive-1135
Diffs
-----
trunk/build.xml 953531
trunk/hwi/web/set_processor.jsp 953531
trunk/xdocs/docs/glossary.xml PRE-CREATION
trunk/xdocs/docs/index.xml PRE-CREATION
trunk/xdocs/docs/language_manual/data-manipulation-statements.xml PRE-CREATION
trunk/xdocs/docs/language_manual/working_with_bucketed_tables.xml PRE-CREATION
trunk/xdocs/docs/user/hwi.xml PRE-CREATION
trunk/xdocs/site.css PRE-CREATION
trunk/xdocs/stylesheets/project.xml PRE-CREATION
trunk/xdocs/stylesheets/site.vsl PRE-CREATION
trunk/xdocs/velocity.properties PRE-CREATION
Diff: http://review.hbase.org/r/178/diff
Testing
-------
Thanks,
Carl
> 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "John Sichi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882447#action_12882447 ]
John Sichi commented on HIVE-1135:
----------------------------------
I should be able to get to this one early next week.
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Fix Version/s: 0.6.0
Affects Version/s: 0.5.0
> 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, 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882349#action_12882349 ]
Edward Capriolo commented on HIVE-1135:
---------------------------------------
Bump:: I will fix the formatting later. Can we commit this we do not really need any unit tests here?
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Attachment: hive-1135-6-patch.txt
hive-1136-6-patch.txt:
* Use Ivy to manage jdom dependency for docs target.
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and
tutorial to version control
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879586#action_12879586 ]
HBase Review Board commented on HIVE-1135:
------------------------------------------
Message from: "Carl Steinbach" <ca...@cloudera.com>
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.hbase.org/r/178/
-----------------------------------------------------------
(Updated 2010-06-16 16:51:58.636162)
Review request for Hive Developers.
Changes
-------
Updated diff.
Summary
-------
Submitted on behalf of Ed Capriolo.
This addresses bug hive-1135.
http://issues.apache.org/jira/browse/hive-1135
Diffs (updated)
-----
trunk/build.xml 955109
trunk/docs/docs/index.xml PRE-CREATION
trunk/docs/docs/language_manual/data-manipulation-statements.xml PRE-CREATION
trunk/docs/docs/language_manual/working_with_bucketed_tables.xml PRE-CREATION
trunk/docs/site.css PRE-CREATION
trunk/docs/stylesheets/project.xml PRE-CREATION
trunk/docs/stylesheets/site.vsl PRE-CREATION
trunk/docs/velocity.properties PRE-CREATION
Diff: http://review.hbase.org/r/178/diff
Testing
-------
Thanks,
Carl
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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-1135-3-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Status: Patch Available (was: Open)
> 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, 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880297#action_12880297 ]
Carl Steinbach commented on HIVE-1135:
--------------------------------------
@Ed:
* I updated the patch to use Ivy for managing the JDOM dependency.
* I'm not sure how to fix the image alignment issue. Let's defer worrying about this for a followup ticket.
* I will file a followup ticket that covers migrating the wiki docs over to version control. We need to do this in a consistent fashion in order to avoid missing any updates to the wiki that people make in the meantime. We also need to figure out how to push the generated docs to the website.
* I'm +1 for committing this patch. Can you take care of that?
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Affects Version/s: (was: 0.5.0)
Fix Version/s: (was: 0.7.0)
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> Key: HIVE-1135
> URL: https://issues.apache.org/jira/browse/HIVE-1135
> Project: Hadoop Hive
> Issue Type: Task
> Components: Documentation
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Fix For: 0.6.0
>
> Attachments: hive-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Fix Version/s: 0.7.0
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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, 0.7.0
>
> Attachments: hive-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: wtf.png
Cool on adding the logo....But something went wrong here. Unless I applied the patch from the left table looks wrong now. check the screen shot.
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: hive-1335-2.patch.txt
Edited the build.xml a bit to deal with some incorrect paths. Also added the HiveDataDefinitionStatements wiki page for reference. Is everyone ok with using anakia and this structure. I would like to get this cleaned up with the current docs in place. Then I will do some follow up tickets and add some wiki pages, let me know if everyone is happy with the overall xdocs->docs process.
> 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884141#action_12884141 ]
Edward Capriolo commented on HIVE-1135:
---------------------------------------
Carl, thank you for the assist!
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "John Sichi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Sichi updated HIVE-1135:
-----------------------------
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Resolution: Fixed
Committed. Thanks Edward!
Carl, could you open another JIRA issue for getting all the relevant docs moved from wiki to Anakia as part of 0.6 release, and also send out coordinating instructions on the mailing list so that people know about the change?
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: jdom-1.1.jar
> 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
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Attachments: 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.
[jira] Updated: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Status: Open (was: Patch Available)
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and all wiki
based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: hive-1335-1.patch.txt
Patch, docs command beings anakia from xdocs directory.
> 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, 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878779#action_12878779 ]
HBase Review Board commented on HIVE-1135:
------------------------------------------
Message from: "Carl Steinbach" <ca...@cloudera.com>
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.hbase.org/r/178/#review217
-----------------------------------------------------------
Looks good overall.
A couple suggestions:
* Stash this stuff under docs/ instead of creating another top level directory (xdocs/)
* Manage the jdom dependency with Ivy.
* 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.
trunk/build.xml
<http://review.hbase.org/r/178/#comment982>
I think it would be good to use the full name ("anakia") instead of abbreviating it as "an".
trunk/build.xml
<http://review.hbase.org/r/178/#comment985>
Please add a description so that this shows up in the output of 'ant -p'
trunk/build.xml
<http://review.hbase.org/r/178/#comment986>
Can we rename this "check-for-anakia" and remove the "prepare-error" target, i.e. something similar to the way the checkstyle check is currently done?
trunk/hwi/web/set_processor.jsp
<http://review.hbase.org/r/178/#comment987>
Did you mean to include this in the patch?
trunk/xdocs/docs/glossary.xml
<http://review.hbase.org/r/178/#comment988>
This email address looks bogus. Perhaps this should be hive-dev@hadoop.apache.org? Or else leave it out entirely?
Is the author property something that we can define in velocity.properties?
trunk/xdocs/stylesheets/project.xml
<http://review.hbase.org/r/178/#comment993>
Let's try to stick with consistent indentation (2 characters).
trunk/xdocs/stylesheets/site.vsl
<http://review.hbase.org/r/178/#comment995>
ASF header repeated twice.
- Carl
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HIVE-1135) Move hive language manual and tutorial
to version control
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Status: Patch Available (was: Open)
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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-1135-3-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE
>
>
> 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "John Sichi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883380#action_12883380 ]
John Sichi commented on HIVE-1135:
----------------------------------
+1. Will commit if tests pass (I can't think why they wouldn't but hey).
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Commented: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880303#action_12880303 ]
Edward Capriolo commented on HIVE-1135:
---------------------------------------
Great on ivy.
As for the wiki I think we should just put a node at the top of the page that says "Do not edit me. Edit xdocs instead." For the pages we have migrated. I want to do like a page every other day so it should be done soon enough. I actually have commit access but I usually leave the commits up to the experts. Also since I worked on this ticket I really should not be the commit person. Anyone else?
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1135-6-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830428#action_12830428 ]
Edward Capriolo commented on HIVE-1135:
---------------------------------------
Jeff,
I only knew the other projects used forest. Anakin sounds good just because it is an apache project. I do not have any experience with any of these. I was more focused on having documentation to match the branches.
> 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
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
>
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830423#action_12830423 ]
Jeff Hammerbacher commented on HIVE-1135:
-----------------------------------------
I'd suggest using something other than forrest for the official documentation. See https://issues.apache.org/jira/browse/AVRO-319 for some suggested replacements.
> 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
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and tutorial
to version control
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-1135:
---------------------------------
Attachment: hive-1135-4-patch.txt
* Fixed broken image links in the stylesheet.
* Moved docs/docs/ to docs/xdocs/
* Added description to ant 'docs' target.
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and tutorial
to version control
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: jdom-1.1.LICENSE
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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-1135-3-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE
>
>
> 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.
[jira] Commented: (HIVE-1135) Move hive language manual and all
wiki based documentation to forest
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878818#action_12878818 ]
Edward Capriolo commented on HIVE-1135:
---------------------------------------
>JDOM ivy.
Right now most/all the stuff in /lib DOES NOT comes from ivy. We should open up a another ticket and convert the entire project to ivy.
> 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.
[jira] Updated: (HIVE-1135) Use Anakia for version controlled
documentation
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: hive-1135-5-patch.txt
Added the join page as well.
> Use Anakia for version controlled documentation
> -----------------------------------------------
>
> 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-1135-3-patch.txt, hive-1135-4-patch.txt, hive-1135-5-patch.txt, hive-1335-1.patch.txt, hive-1335-2.patch.txt, jdom-1.1.jar, jdom-1.1.LICENSE, wtf.png
>
>
> 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.
[jira] Updated: (HIVE-1135) Move hive language manual and tutorial
to version control
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Capriolo updated HIVE-1135:
----------------------------------
Attachment: hive-1135-3-patch.txt
Fixed all items.
> Move hive language manual and tutorial to version control
> ---------------------------------------------------------
>
> 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-1135-3-patch.txt, 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.