[ 
https://issues.apache.org/jira/browse/PARQUET-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808877#comment-16808877
 ] 

Zoltan Ivanfi commented on PARQUET-1556:
----------------------------------------

That's a very good point, thanks for raising it. We don't use Hadoop-LZO 
ourselves. Running {{mvn dependency:tree}} shows that this is a compile-time 
transitive dependecy:
{code}
[INFO] org.apache.parquet:parquet-thrift:jar:1.12.0-SNAPSHOT
[INFO] +- com.twitter.elephantbird:elephant-bird-core:jar:4.4:compile
[INFO] |  \- com.hadoop.gplcompression:hadoop-lzo:jar:0.4.16:compile
{code}

Before adding it to the POM we have to understand:
* Why it can be downloaded for most people even without a corresponding repo 
entry.
* Why it fails for others.
* What it would mean to add the repo to the POM (would it lead to shipping a 
GPL dependency).
* Can we avoid pulling this in all together?

> Add twitter maven repo to POM for hadoop-lzo dependency
> -------------------------------------------------------
>
>                 Key: PARQUET-1556
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1556
>             Project: Parquet
>          Issue Type: Improvement
>    Affects Versions: 1.11.0
>            Reporter: Andy Grove
>            Assignee: Andy Grove
>            Priority: Major
>             Fix For: 1.12.0
>
>
> Running mvn verify based on the instructions in the README results in this 
> error
> {code:java}
> Could not resolve dependencies for project 
> org.apache.parquet:parquet-thrift:jar:1.11.0: Could not find artifact 
> com.hadoop.gplcompression:hadoop-lzo:jar:0.4.16{code}
> As a workaround, the local ~/.m2/settings.xml file can be modified to include 
> the twitter maven repo:
> {code:java}
> <repository>
>   <id>twitter</id>
>   <name>twitter</name>
>   <url>http://maven.twttr.com</url>
> </repository>
> {code}
> After adding this, {{mvn verify}} works. The proper solution, however, is to 
> include this repo in the POM files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to