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

split library/deployment jar to separate cascading, hive, pig and raw mapreduce #86

ppat opened this Issue Sep 14, 2013 · 1 comment


None yet
2 participants
Copy link

ppat commented Sep 14, 2013

We only use Cascading. Having Hive/Pig dependencies greatly complicate our dependency tree and make it bit harder to manage our existing dependencies. Would be great if we can separate these.

See convo on google group here!topic/elasticsearch/90eCJr4vJHU


This comment has been minimized.

Copy link

costin commented Apr 2, 2014


This has been fixed in master. see #182

@costin costin closed this Apr 2, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.