Hi Keegan, Unfortunately, at the time of the module split in 0.96, we could not completely decouple mapreduce classes from the server dependencies. I think we actually need two modules to be extracted out, one is hbase-mapreduce (probably separate module than client module) and hbase-storage for the storage bits. I am sure at some point that will happen.
Enis On Tue, May 13, 2014 at 9:09 AM, Keegan Witt <[email protected]> wrote: > Possibly this was due to HBASE-7186 or HBASE-7188. It's especially odd > since I don't see usages outside the mapreduce package (at least for the > classes that were of interest to me), so there shouldn't be any issue with > changing the artifact the package is deployed in. > Is this more a question for the dev list? > > -Keegan > > > On Thu, May 1, 2014 at 10:59 AM, Keegan Witt <[email protected]> wrote: > > > It looks like maybe as part of HBASE-4336, classes under the mapred and > > mapreduce package are now deployed in the hbase-server artifact. > Wouldn't > > it make more sense to have these deployed in hbase-client? hbase-server > is > > a pretty big artifact to pull down to get access to TableOutputFormat, > for > > example. > > > > If this makes sense, I can open a Jira. I just thought I'd see if > someone > > could explain the rationale first. Thanks! > > > > -Keegan > > >
