On Wed, Oct 25, 2017 at 9:53 PM, Sean Busbey <bus...@apache.org> wrote:
> > okay so here's a use case. our return from `hbase classpath` is a > nightmare. if you're a downstream user that just wants "hey hbase give > me jars I need to run against you right now." it's garbage. we could > include the shaded jars and return the shaded client for something > like `hbase classpath-client`. Same with replacing `hbase mapredcp` > current output with the shaded mapreduce jar. > I think the listing of dependencies provided by `hbase classpath` family of utilities an anti-pattern in light of shaded artifacts. Can we replace these commands with instructions to build your application jar with the appropriate dependencies? Are there use-cases where the user doesn't control their classpath, they have no choice but to use `hadoop`/`yarn` to launch their application instead of `hbase`?
