Hi Lekhnath, The IntSets are package protected so that their callers will always use the IntSet interface, thus preventing manipulation of the IntSet after it was built and hiding implementation details. It seems to me that having an index which can spill to disk may be a handy feature, perhaps you can create a patch with your suggested changes/additions? The latest version of IHBASE can be obtained from http://github.com/ykulbak/ihbase
Cheers, Yoram On Mon, May 10, 2010 at 9:17 PM, Lekhnath <lbhu...@veriskhealth.com> wrote: > Hi folks, > I have to use numerous search criteria and each having lots of distinct > values. So, the secondary indexing like IHBase will require lots of memory. > I think I require a custom index implementation in which I decided to > persist some of the IHBase like implementation. For that case I need to > reuse the IHBase' IntSet implementations. They are package protected so that > I could not extend the implementation and am forced to rewrite the code. > Is there any good reason why the implementations are package protected. > > Thanks, > Lekhnath > > > > This email is intended for the recipient only. If you are not the intended > recipient please disregard, and do not use the information for any purpose. >
