[ 
https://issues.apache.org/jira/browse/GOBBLIN-1180?focusedWorklogId=440996&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-440996
 ]

ASF GitHub Bot logged work on GOBBLIN-1180:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Jun/20 21:28
            Start Date: 03/Jun/20 21:28
    Worklog Time Spent: 10m 
      Work Description: vikrambohra closed pull request #3026:
URL: https://github.com/apache/incubator-gobblin/pull/3026


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 440996)
    Time Spent: 40m  (was: 0.5h)

> Remove dependency on gobblin-parquet
> ------------------------------------
>
>                 Key: GOBBLIN-1180
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1180
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Vikram Bohra
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> gobblin-parquet has dependencies on com.twitter  parquet libraries.
> 'com.twitter:parquet-protobuf:1.5.0' (including higher versions) is not 
> resolvable from MavenCentral because it's missing some of its transitive 
> dependencies. This makes the 'gobblin-parquet' module _also not resolvable_ 
> from MavenCentral (e.g. 'org.apache.gobblin:gobblin-parquet:0.14.0' does not 
> resolve from Central as of today).
> To fix this, I suggest using "gobblin-parquet-apache" (which has org.apache 
> parquet libraries) instead of "gobblin-parquet" 
> This also unblocks automated consumption of gobblin external artifact at 
> LinkedIn
> After this change, gobblin-parquet module can safely be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to