Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hadoop-lzo jar resolution #62

Open
jglesner opened this issue Nov 11, 2019 · 4 comments
Open

hadoop-lzo jar resolution #62

jglesner opened this issue Nov 11, 2019 · 4 comments
Assignees

Comments

@jglesner
Copy link
Contributor

jglesner commented Nov 11, 2019

Hello,

I'm running into an issue using the latest fsqio master where ivy is consistently unable to resolve hadoop-lzo and fails to run serve.py.

[NOT FOUND ] com.hadoop.gplcompression#hadoop-lzo;0.4.19!hadoop-lzo.jar (0ms)
==== maven.twttr.com-maven: tried
https://maven.twttr.com/com/hadoop/gplcompression/hadoop-lzo/0.4.19/hadoop-lzo-0.4.19.jar

I'm not all too familiar with the dependency management aspects of twofishes. I'm running this from an ubuntu 14.04 docker container, and everything has worked historically ... until now. Any recommendations on how to figure out what's going on / solve for this? I would greatly appreciate it.

Strangely, when I git clone the fsqio repo, and run serve.py from the command line on an Amazon Linux 1 EC2 instance it works perfectly. No dependency issues. I need to run it from a docker container, though preferably.

@jglesner
Copy link
Contributor Author

Not sure if this is the correct fix, but I was able to get past this issue by adding a new global exclusion to Ivy by editing the pants.ini file under [resolve.ivy]:
{"org": "com.hadoop.gplcompression", "name": "hadoop-lzo"},

@mateor
Copy link
Contributor

mateor commented Nov 14, 2019

I think that your fix is likely the right answer. We are getting ready to update fsq.io, would you be interested in sending a PR?

@jglesner
Copy link
Contributor Author

jglesner commented Nov 14, 2019 via email

@mateor
Copy link
Contributor

mateor commented Nov 14, 2019

That sounds great! The update is addressing unrelated bug in our dependencies, so we may need to land that first in order to get the build green anyway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants