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 >> Where to place HTable.exists() tests?


+
Jean-Marc Spaggiari 2013-01-05, 16:30
Copy link to this message
-
Re: Where to place HTable.exists() tests?
Hi,

Look at the tests in the client package. Typically TestFromClientSide.
You may want to write some 'pure' unit test as well (i.e. small category).
Then you may want to create a specific class.
And I wouldn't be against a test class for HTable, especially is it can be
one that doesn't start a cluster.

In all cases, public boolean[] exists(Get[] gets) is not good imho.
You need this to be consistent with the API:
public Boolean[] exists(List<Get> gets)

Boolean and not boolean to manage the failures (null means failure for this
get).
List vs. array purely for consistency.

Cheers,

Nicolas
On Sat, Jan 5, 2013 at 5:30 PM, Jean-Marc Spaggiari <[EMAIL PROTECTED]
> wrote:

> public boolean[] exists(Get[] gets
+
Jean-Marc Spaggiari 2013-01-05, 17:35
+
Nicolas Liochon 2013-01-05, 17:49
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