[ 
https://issues.apache.org/jira/browse/TEZ-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hitesh Shah updated TEZ-2243:
-----------------------------
    Attachment: TEZ-2243.1.modified.patch

Thanks [~michaelthoward] . Sorry for the delay in reviewing the patch.

I modified the patch slightly to be less verbose with respect to the rpm bone 
urls but the overall patch looked good.

Will commit shortly. 

As for testing markdown changes, you can run "mvn site" from the docs 
directory. This will generate the html into /docs/target which you can then 
review manually.  

> documentation should explicitly specify protobuf 2.5.0
> ------------------------------------------------------
>
>                 Key: TEZ-2243
>                 URL: https://issues.apache.org/jira/browse/TEZ-2243
>             Project: Apache Tez
>          Issue Type: Task
>    Affects Versions: 0.6.0
>            Reporter: Michael Howard
>            Priority: Minor
>              Labels: documentation, newbie
>         Attachments: TEZ-2243.1.modified.patch, installDocProtobuf250.patch
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> Install guide doc at 
> http://tez.apache.org/install.html 
> says:
> > ... Protocol Buffers (protoc compiler) 2.5 or later
> In fact, protobuf 2.5.0 is required. 
> On a Mac, both the libraries and the protobuf-compiler can be installed with:
> $ brew install protobuf250
> The yum repos on my CentOS system included epel & epel-testing. 
> Nevertheless, they were only at protobuf 2.3.0
> I used rpm.pbone.net and found the following:
> protobuf-2.5.0-16.1.x86_64.rpm
> protobuf-compiler-2.5.0-16.1.x86_64.rpm
> at
> http://rpm.pbone.net/index.php3/stat/4/idpl/23552166/dir/centos_6/com/protobuf-2.5.0-16.1.x86_64.rpm.html
> http://rpm.pbone.net/index.php3/stat/4/idpl/23552097/dir/centos_6/com/protobuf-compiler-2.5.0-16.1.i686.rpm.html
> Hitesh Shah wrote:
> > Pretty much all of the Hadoop ecosystem components have standardized on 
> > protobuf-2.5.0. 
> Hitesh Shah wrote:
> > Could you file a jira and submit a patch for this issue 
> Sorry, I don't know how to submit a patch. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to