-
Notifications
You must be signed in to change notification settings - Fork 178
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
Why use out of date hadoop-core instead of replacement hadoop-common? #303
Comments
The only thing preventing this change is a solid maintainer. If you'd be
|
Hi @sritchie, I would like spending my spare time maintaining cascalog, I used it in production in 2014[1], since then move on to other fields, but still related to Hadoop and clojure thing. [1]: https://github.com/jiacai2050/hebo this is the project to schedule cascalog jobs. |
@jiacai2050, I'm sure that's fine. I'm so out of the loop that I don't really understand what needs work, but if you have anything you'd like to work on I could probably help code review while you get spun up. Thanks for thinking of Cascalog! |
Thanks. |
@jiacai2050 I've been out of the Cascalog game for maybe 6 years now so unfortunately I don't. Best of luck! |
Shouldn't
hadoop-common
be used in place ofhadoop-core
in the dependencies of the various Cascalog projects, per this stackoverflow question or is there something else keeping it from being updated/changed to usehadoop-common
or evenhadoop-client
instead ofhadoop-core
.The text was updated successfully, but these errors were encountered: