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

Move MiniFluo to its own module/jar #439

Closed
keith-turner opened this issue Mar 17, 2015 · 1 comment
Closed

Move MiniFluo to its own module/jar #439

keith-turner opened this issue Mar 17, 2015 · 1 comment
Milestone

Comments

@keith-turner
Copy link
Contributor

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.

@keith-turner keith-turner added this to the 1.0.0 milestone Mar 17, 2015
@keith-turner
Copy link
Contributor Author

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 mikewalch modified the milestones: 1.0.0-beta-1, 1.0.0 May 6, 2015
@mikewalch 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 mikewalch self-assigned this 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants