Hi there,

On top of what Vladimir already saidŠ

re:  "Table1: 80 m records say Author, Table2 : 5k records say Category"

Just 80 million records?  Hbase tends to be overkill for relatively low
data volumes.

But if you wish to proceed this path, to extend what was already said,
rather than thinking of it in terms of an RDBMS 2 table design, create a
pre-joined table that has data from both tables as the query target.
As for the LRU cache, ³premature optimization is the root of all evil².

Best of luck!
On 2/24/14, 4:38 PM, "Vikram Singh Chandel" <[EMAIL PROTECTED]>

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