-
Notifications
You must be signed in to change notification settings - Fork 78
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Move MiniFluo to its own module/jar #439
Milestone
Comments
I think mini accumulo also depends on mini dfs, which brings in server side hadoop deps. It would be nice to not require all of these server side deps for Fluo client code. |
mikewalch
changed the title
Consider putting mini fluo in own jar
Move MiniFluo to its own module/jar
May 6, 2015
mikewalch
added a commit
to mikewalch/fluo
that referenced
this issue
May 6, 2015
mikewalch
added a commit
to mikewalch/fluo
that referenced
this issue
May 6, 2015
mikewalch
added a commit
to mikewalch/fluo
that referenced
this issue
May 6, 2015
mikewalch
added a commit
to mikewalch/fluo
that referenced
this issue
May 7, 2015
mikewalch
added a commit
that referenced
this issue
May 7, 2015
Closes #439 - Move MiniFluo to its own module/jar
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mini fluo is currently in fluo-core. As a result fluo-core depends on accumulo-minicluster, which in turn depends on Accumulo tserver, master, and gc code. If mini-fluo were in its own jar, then a user could avoid these dependencies if needed.
The text was updated successfully, but these errors were encountered: