Hi William, I'd recommend looking at supporting these HBase features through the standard SQL merge statement where they compile down to these native calls when possible. Also, with our transaction support, you can already do an increment atomically and retry if a conflict occurs. Thanks, James
On Tuesday, May 3, 2016, William <[email protected]> wrote: > Hi all, > I am trying to support hbase Increment and checkAndPut/checkAndDelete > in phoenix and have done with Increment by introducing a new statement > INCREMENT. > Grammar: > INCREMENT tableName (column defs) VALUES(....) where expressions > > > Because all increment operations can be stored in a single Increment > object which can be committed by Table#batch(), it is not hard to do the > job. > But for checkAndPut/checkAndDelete, there isn't such a class that holds > the conditions and values at the same time. And for the existed write > path, all methods and data structures are > used to generate List<Mutation>, it is hard to add a new data type to the > write path. So I have to create a new write path. > May someone give me some advice or solutions? > Thanks. > > > William
