cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David McNelis <dmcne...@agentisenergy.com>
Subject Re: Multiple indexes - how does Cassandra handle these internally?
Date Mon, 24 Jan 2011 01:35:12 GMT
Silly question, M us thousand or million?  In print, thousand is M, fwiw

Sent from my Droid
On Jan 23, 2011 7:26 PM, "Maxim Potekhin" <potekhin@bnl.gov> wrote:
> Aaron -- thanks!
>
> I don't have examples like Timo.
>
> But,
>
> I'm keen to use multiple indices over a database
> of 300M rows.
>
>
> Maxim
>
>
> On 1/23/2011 3:28 PM, Aaron Morton wrote:
>> Timo / Maxim
>> Could you provide a more concrete example and I'll try to look into it
tonight.
>>
>> Cheers
>> Aaron
>>
>>
>> On 22/01/2011, at 5:01 AM, Maxim Potekhin<potekhin@bnl.gov> wrote:
>>
>>> Well it does sound like a bug in Cassandra. Indexes MUST commute.
>>>
>>> I really need this functionality, it's a show stopper for me...
>>>
>>> On 1/21/2011 10:56 AM, Timo Nentwig wrote:
>>>> On Jan 21, 2011, at 16:46, Maxim Potekhin wrote:
>>>>
>>>>> But Timo, this is even more mysterious! If both conditions are met, at
least
>>>>> something must be returned in the second query. Have you tried this in
CLI?
>>>>> That would allow you to at least alleviate client concerns.
>>>> I did this on the CLI only so far. So value comparison on the index
seems to be done differently than in the nested loop...or something. Don't
know, don't know the code base well enough to debug this down to the very
bottom either. But it's actually only a CF with 2 cols (AsciiType and
IntegerType) and a command in the CLI so not too time-consuming to
reproduce.
>

Mime
View raw message