I am wondering why we have a tiered index in the HFile format. Is it because the root index must fit in memory - hence must be limited in size. Does the bound on the root index pretty much dictate the index tiers ?
We used to hold the entire HFile index in memory, although you could trade off between the size of the index and amount of IO required to find the desired records. Facebook found the aggregate size of indexes far too large for their use case(s) so included the tiered index in the HFile V2 redesign. The design documents on HBASE-3857 might be worth a look. On Mon, Jul 14, 2014 at 11:14 AM, Varun Sharma <[EMAIL PROTECTED]> wrote: Best regards,
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Cheers On Mon, Jul 14, 2014 at 11:14 AM, Varun Sharma <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext