[Discussion] Dependencies and integration modules

[cjnolet]

Currently, the Graph Store Recipe has tinkerpop dependencies in it. For writing pig loaders, should pig dependencies be introduced into the stores? I was thinking the following layout may be a little more useful:

$ROOT/store/entity-store/pig $ROOT/store/entity-store/core

That way the Tinkerpop could be

$ROOT/store/graph-store/core $ROOT/store/graph-store/tinkerpop

There could be other ways to do this too... like having $ROOT/store/pig with all the pig modules for all the stores. Thing is, then the tinkerpop integration would only exist in $ROOT/store/tinkerpop for a single store, ever.

[eawagner]

I vote for the

$ROOT/store/pig $ROOT/store/tinkertop

1. I think this has several advantages. If we add all the pig integrations into a single project then it make deployment much easier if you are using multiple stores.
2. it keeps all utility code related to integrating with pig in its own area instead of in commons or mango so that it can be shared around more easily with all the pig subprojects.
3. Makes it easier to find in one place what has Pig or tinkertop integration instead of browsing sub-projects or (possibly out of date) documentation.