Blob stores do not have the same semantics as file systems. HBase relies on very specific semantics with respect to concurrency and atomic operations which most blob stores (including S3) do not provide. One example: a move of some "directory" in an S3 bucket is not atomic whereas this is atomic in HDFS. HBase will 100% not work correctly if you try to configure hbase.rootdir to use S3 via the S3A adapter in Hadoop. EMR has proprietary code in their S3 filesystem access layer, unique from S3A, which does not suffer from this issue somehow. ... View more

HBase 0.94 and 0.95 are extremely old versions. You should not be using them any longer. In general, you should use the same exact version of client jars which match the HBase cluster version you are trying to interact with. ... View more

hbase(main):001:0> help 'scan' Scan a table; pass table name and optionally a dictionary of scanner specifications.  Scanner specifications may include one or more of: TIMERANGE, FILTER, LIMIT, STARTROW, STOPROW, ROWPREFIXFILTER, TIMESTAMP, MAXLENGTH or COLUMNS, CACHE or RAW, VERSIONS, ALL_METRICS or METRICS ... Some examples: ...   hbase> scan 't1', {COLUMNS => 'c1', TIMERANGE => [1303668804000, 1303668904000]} ... View more