Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # dev >> multi() contract or lack thereof


+
Sergey Shelukhin 2014-01-06, 23:32
Copy link to this message
-
Re: multi() contract or lack thereof
Suppose some actions in a multi call fail. Do we change the index during
retry?
On Mon, Jan 6, 2014 at 3:32 PM, Sergey Shelukhin <[EMAIL PROTECTED]>wrote:

> Hi.
> Looking at code, the way multi currently works is that either the entire
> thing fails with an exception, or multiresponse is returned with exactly
> one result/exception per action in multiaction, in corresponding order.
> This sounds like a reasonable API contract, but it could be "by accident".
> Do you think we can rely on this remaining true?
> That way I can remove passing action index from client back and forth thru
> the server (with backward compat ofc).
>
> --
> CONFIDENTIALITY NOTICE
> 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.
>
+
Sergey Shelukhin 2014-01-06, 23:55
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