We need to revisit which interfaces should be marked as real "private"
because coprocessors allow custom applications to accesses internal
states. Current private interface such as KeyValue, WALEdit, Hregion,
HLogKey, Store etc is may used by custom coprocessor applications so any
public method signature change in those "private" interfaces possibliy
breaks custom coprocessor implementations.


On 2/10/14 4:59 PM, "lars hofhansl" <[EMAIL PROTECTED]> wrote:
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB