[jira] Commented: (HIVE-1135) Move hive language manual and all wiki based documentation to forest

2010-06-14 Thread Edward Capriolo (JIRA) 

[ 
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] Commented: (HIVE-1135) Move hive language manual and all wiki based documentation to forest

2010-06-14 Thread Edward Capriolo (JIRA) 

[ 
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] Commented: (HIVE-1135) Move hive language manual and all wiki based documentation to forest

2010-06-14 Thread HBase Review Board (JIRA) 

[ 
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" 


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) Move hive language manual and all wiki based documentation to forest

2010-06-14 Thread HBase Review Board (JIRA) 

[ 
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" 

---
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


I think it would be good to use the full name ("anakia") instead of 
abbreviating it as "an".



trunk/build.xml


Please add a description so that this shows up in the output of 'ant -p'



trunk/build.xml


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


Did you mean to include this in the patch?



trunk/xdocs/docs/glossary.xml


This email address looks bogus. Perhaps this should be 
hive-...@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


Let's try to stick with consistent indentation (2 characters).



trunk/xdocs/stylesheets/site.vsl


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

2010-06-14 Thread HBase Review Board (JIRA) 

[ 
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" 

---
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) Move hive language manual and all wiki based documentation to forest

2010-02-05 Thread Edward Capriolo (JIRA) 

[ 
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

2010-02-05 Thread Jeff Hammerbacher (JIRA) 

[ 
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.