cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Hobbs <ty...@datastax.com>
Subject Re: Composite Slice Query returning non-sliced data
Date Tue, 10 Jul 2012 19:30:33 GMT
On Tue, Jul 10, 2012 at 2:20 PM, Sunit Randhawa <sunit.randhawa@gmail.com>wrote:

> I have tested this extensively and EOC has huge issue in terms of
> usability of CompositeTypes in Cassandra.
>
> As an example: If you have 2 Composite Columns such as A:B:C and A:D:C.
>
> And if you do search on A:B as start and end Composite Components, it
> will return D as well. Because it returns all the remaining columns
> from your start range.
>

That shouldn't be happening, and I can test that it works correctly using
pycassa.  So I suspect a problem with Hector.


>
> Similarly if you do search on A:D as start and end Composite
> Components, it will not return B because the D comes after B.
>

This is expected behavior.


>
> Sadly, the information given here on intro to composite Types:
> http://www.datastax.com/dev/blog/introduction-to-composite-columns-part-1
> also does not work.
>
> On Tue, Jul 10, 2012 at 9:24 AM, Tyler Hobbs <tyler@datastax.com> wrote:
> > I think in this case that's just Hector's way of setting the EOC byte
> for a
> > component.  My guess is that the composite isn't being structured
> correctly
> > through Hector, as well.
> >
> >
> > On Tue, Jul 10, 2012 at 4:40 AM, aaron morton <aaron@thelastpickle.com>
> > wrote:
> >>
> >>
> >> The first thing that stands out is that (in cassandra) comparison
> >> operations are not used in a slice range.
> >
> >
> >
> >
> > --
> > Tyler Hobbs
> > DataStax
> >
>



-- 
Tyler Hobbs
DataStax <http://datastax.com/>

Mime
View raw message