Hi Yoram,
Thanks for your reply. We have structural data and have to search and
sort against each attribute. So, simply IHBase or THBase did not help.
We are studying on some custom implementation that is in between IHBase
and THBase. For that case we may need Coprocessors implemented in HBase.
Besides that we are in need of extending IntSet implementation that
spills to disk. Lets see if customization of IHBase with some feature
added will help. If so, we will definitely choose to extend IHBase.
Thanks,
Lekhnath
On 5/12/2010 6:20 PM, Ram Kulbak wrote:
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<[email protected]> 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.
.
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.
