Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # user - CCIndex for cassandra


Copy link to this message
-
Re: CCIndex for cassandra
Andrew Purtell 2013-02-27, 04:32
You are mailing a HBase mailing list. Since your only interest seems centered around Cassandra, you should ask your question on a mailing list of theirs.

On Feb 26, 2013, at 8:29 PM, bjbhutkar <[EMAIL PROTECTED]> wrote:

> The thing I am interested in is in correspondence with cassandra. Cassandra
> currently supports multidimensional range queries with a limitation that at
> least one of the dimensions supplied in the query must be of equality
> operation
> example : "Select * from table where Weight > 65 AND Height < 6 AND Country
> = India" . This is supported in cassandra.
> But "Select * from table where Weight > 65 AND Height < 6" this query  is
> not possible with current cassandra version. To mitigate this problem I
> thought of implementing the CCIndex in cassandra as the paper claims to
> provide such functionality.
>
> I searched around and found the code for CCIndex on github . I was
> wondering whether this code can be modified so that it uses Cassandra's
> APIs. Furthermore , If anybody's having any suggestions for implementing
> such functionality then please let me know . Is such functionality provided
> in HBase or not ? If yes , then how the algorithm works for querying the
> data where all the dimensions in a query are either "Less Than (<) "or "Greater
> Than (>)" ?
>
>
>
> On Wed, Feb 27, 2013 at 7:14 AM, Jean-Marc Spaggiari [via Apache HBase] <
> ml-node+[EMAIL PROTECTED]> wrote:
>
>> Hi Bhalchandra,
>>
>> This is a 3 years old PDF, and still, I'm not able to find any trace
>> of that in HBase anywhere. Sorry. Seems that it was based on HBase
>> 0.20.1. We are now at 0.94.5...
>>
>> Maybe it's a vendor extension which has not been published/released?
>>
>> JM
>>
>> 2013/2/26 bjbhutkar <[hidden email]<http://user/SendEmail.jtp?type=node&node=4039285&i=0>>:
>>
>>
>>> Hi Jean Marc
>>>
>>> HBase implementation of CCIndex in the following link
>>>
>>> http://www.china-cloud.com/ziliao/CCIndex%20HBase.pdf
>>>
>>>
>>> On Tue, Feb 26, 2013 at 11:28 AM, bhalchandra bhutkar <
>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=4039285&i=1>>
>> wrote:
>>>
>>>> Dear Jean Marc ,
>>>>
>>>> Thanks for responding.
>>>> CCIndex stands for Complemental Clustering Index. The reference for
>>>> CCIndex can be found in following ink
>> http://www.slideshare.net/jgabriellima/cc-index-for-cassandra-a-novel-scheme-for-multidimensional-range-queries-in-cassandra
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Feb 25, 2013 at 7:01 AM, Jean-Marc Spaggiari [via Apache HBase]
>> <
>>>> [hidden email] <http://user/SendEmail.jtp?type=node&node=4039285&i=2>>
>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> What do you mean by CCIndex?
>>>>>
>>>>> The only thing I found about that is
>> https://github.com/Jia-Liu/CCIndex and
>>>>>
>>>>> it has not been updated for 2 years now.
>>>>>
>>>>> Also found that wich is more recent:
>>>>> https://github.com/ICT-Ope/CCIndex_HBase_0.90.0
>>>>>
>>>>> You can also read this thread:
>>>>> http://www.mail-archive.com/dev@.../msg06553.html<
>> http://www.mail-archive.com/dev@.../msg06553.html<http://www.mail-archive.com/[EMAIL PROTECTED]/msg06553.html>>
>>
>>>>>
>>>>> Looking at the code I was not able to fine any class name close to
>> that
>>>>> neither I found anything into the HBase classes. (Searched for
>>>>> *CC*Index*)
>>>>>
>>>>> All of that to say, I'm not sure this is integrated in HBase today.
>>>>>
>>>>> But I might be wrong. Do you have any reference about what you are
>>>>> looking
>>>>> for?
>>>>>
>>>>> JM
>>>>>
>>>>> 2013/2/24 bjbhutkar <[hidden email]<
>> http://user/SendEmail.jtp?type=node&node=4039078&i=0>>
>>>>>
>>>>>
>>>>>> Hello HBase,
>>>>>>
>>>>>> I am a cassandra user and i want to implement the CCIndex scheme in
>>>>>> cassandra. Can anyone help me to understand the CCIndex code ? I
>> want
>>>>> to
>>>>>> modify the CCIndex code so that it will use the Cassandra's APIs.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context: