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

Zoltan Ivanfi edited comment on PARQUET-1556 at 4/4/19 1:16 PM:
----------------------------------------------------------------

I came to the conclusion that the only possible source of the twitter repo is 
the [POM of the elephant-bird 
dependecy|https://github.com/twitter/elephant-bird/blob/master/pom.xml#L94]. 
However, I have no idea why this doesn't work for you, [~andygrove]. I have 
tried it with both Maven 3.5.2 and 3.6.0 and both are able to download the 
transitive dependecy. What version do you use?


was (Author: zi):
I came to the conclusion that the only possible source of the twitter repo is 
the [POM of the elephant-bird 
dependecy|https://github.com/twitter/elephant-bird/blob/master/pom.xml#L94]. 
However, I have no idea why this doesn't happen for you, [~andygrove]. I have 
tried it with both Maven 3.5.2 and 3.6.0 and both are able to download the 
transitive dependecy. What version do you use?

> 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