GoogleCodeExporter
commented
8 years ago Pardon my ignorance but it seems "simple" to implement, at least for the
mutate() call -- i.e. not for mutateWithDefault().
It seems all that is needed is a asyncMutate() function:
private Future<Long> asyncMutate(Mutator m, String key, int by, long def, int exp)
throws OperationTimeoutException {
final CountDownLatch latch=new CountDownLatch(1);
final OperationFuture<Long> rv=new OperationFuture<Long>(latch,
operationTimeout);
addOp(key, opFact.mutate(m, key, by, def, exp, new OperationCallback() {
public void receivedStatus(OperationStatus s) {
// XXX: Potential abstraction leak.
// The handling of incr/decr in the binary protocol
// Allows us to avoid string processing.
rv.set(new Long(s.isSuccess()?s.getMessage():"-1"));
}
public void complete() {
latch.countDown();
}}));
return rv;
}
Then we can trivially add asyncIncr() and asyncDecr():
public Future<Long> asynIncr(String key, int by) throws OperationTimeoutException {
return asyncMutate(Mutator.incr, key, by, 0, -1);
}
public Future<Long> asyncDecr(String key, int by) throws OperationTimeoutException {
return asyncMutate(Mutator.decr, key, by, 0, -1);
}
Of course mutate() itself would be implemented in terms of asyncMutate():
private long mutate(Mutator m, String key, int by, long def, int exp)
throws OperationTimeoutException {
try
{
return asyncMutate(m, key, by, def, exp).get(operationTimeout,
TimeUnit.MILLISECONDS);
} catch (InterruptedException e) {
throw new RuntimeException("Interrupted waiting for value", e);
} catch (ExecutionException e) {
throw new RuntimeException("Exception waiting for value", e);
} catch (TimeoutException e) {
throw new OperationTimeoutException("Timeout waiting for value", e);
}
}
Now asyncMutateWithDefault() that's a bit more complicated.
No?Original comment by nbrac...@gmail.com on 28 Aug 2008 at 7:18
Original issue reported on code.google.com by
dsalli...@gmail.comon 19 Mar 2008 at 4:52