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 # user >> Problem with HFile lexical comparison


+
Rohit Kelkar 2013-06-19, 17:05
+
Stack 2013-06-19, 17:12
+
Rohit Kelkar 2013-06-19, 17:32
+
Jeff Kolesky 2013-06-19, 18:15
+
Rohit Kelkar 2013-06-20, 00:11
+
Jeff Kolesky 2013-06-20, 00:23
+
Rohit Kelkar 2013-06-20, 04:08
+
Rohit Kelkar 2013-06-20, 19:53
+
Rohit Kelkar 2013-06-20, 22:28
Copy link to this message
-
Re: Problem with HFile lexical comparison
On Thu, Jun 20, 2013 at 3:28 PM, Rohit Kelkar <[EMAIL PROTECTED]> wrote:

>
> Out of curiosity, for my learning, why does LATEST_TIMESTAMP make the table
> not see the actual rows?
>
Because these values will be in the future relative to the host.

When you send a RS an edit w/ LATEST_TIMESTAMP, it will replace
LATEST_TIMESTAMP w/ currentTimeMillis before persisting it. You  by-passed
this facility when you wrote the hfiles yourself.

St.Ack
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