fixes #26 made lock recovery more efficient by caching and batching

That's fine with me if we follow that rule.  If I think something needs to
be commented while I am going through the code, I can just add a comment.

On Fri, Aug 1, 2014 at 11:16 AM, Josh Elser <notifications@github.com>
wrote:

> In modules/core/src/main/java/io/fluo/impl/LockResolver.java:
>
> > +import java.util.Set;
> > +
> > +import org.apache.accumulo.core.client.AccumuloException;
> > +import org.apache.accumulo.core.client.AccumuloSecurityException;
> > +import org.apache.accumulo.core.client.ConditionalWriter;
> > +import org.apache.accumulo.core.client.ConditionalWriter.Status;
> > +import org.apache.accumulo.core.client.IteratorSetting;
> > +import org.apache.accumulo.core.data.ByteSequence;
> > +import org.apache.accumulo.core.data.Condition;
> > +import org.apache.accumulo.core.data.ConditionalMutation;
> > +import org.apache.accumulo.core.data.Key;
> > +import org.apache.accumulo.core.data.Mutation;
> > +import org.apache.accumulo.core.data.Value;
> > +import org.apache.accumulo.core.security.ColumnVisibility;
> > +
> > +public class LockResolver {
>
> "Comments are good" is about the only Accumulo recommendation/guidance. No
> hard-fast rule. I like your points.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/fluo-io/fluo/pull/109/files#r15701192>.
>