History is here: http://www.linkedin.com/groupItem?view=&gid=1407857&type=member&item=5849626646549659651&trk=groups_most_recent-0-b-cmr&goback=.gmr_1407857
Not sure but I think you need to register to the group to read it. Basically, people often complains about coprocs. Like, can not reload them dynamically, need to change the jars names, not well implemented, etc. However, it's still there, and others are using it. The only time I thought about using it, I have been convinced to not do it and ended up using another solution. So was wondering what is the situation around coprocessors. Hope it's more clear now. JM 2014-03-15 18:50 GMT-04:00 Andrew Purtell <[email protected]>: > On Sat, Mar 15, 2014 at 2:40 PM, Jean-Marc Spaggiari < > [email protected]> wrote: > > > This caught my attention on the LinkedIn HBase group: > > > > "Coprocessors are not well thought out or implemented in HBase. " > > > > I'm sorry, but dropping a disparaging statement like that without context > or explanation is the definition of trolling J-M. > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
