+1, plus comments: > What I propose is to retain o.a.h.h.client and o.a.h.h.mapreduce in the next > release, and mark everything in them as deprecated with links to o.a.h stuff > (we may also need to retain o.a.h.h.util since that is used client-side as > well?). We'd also copy both those packages into o.a.h.client/mapreduce where > we'd be able to make non-backwards compatible API changes. For example, > changing HColumnDescriptor to something else (I propose HFamilyDescriptor but > we can deal with this separately).
o.a.h.h.mapred needs to follow too, until it's removed from hadoop. > > One concern is there will be two versions of the same classes in different > packages, but not sure of another way around it. Changing all the class > names would be overkill I think. We already have that with mapred and mapreduce. Project still thriving :) > > Everything that was already marked as deprecated in 0.20 should be removed (I > think this has been done on trunk already). There are still some remaining > references to "column" instead of "family" and also to family:qualifier > notation. I suspect there may always be some limited use cases for that > notation (like weird thing we do to pass in list of columns to MR) but we > should get it out wherever we can. Now that we can pass Scan to MR maybe we > can drop it there too. Yep that's already cleared out. J-D
