Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Partial composite result limit possible?
From: aaron morton <aaron@thelastpickle.com>
In-Reply-To: <372132B6-F983-4573-902F-232382DD8520@broodax.net>
Date: Thu, 16 Aug 2012 09:02:05 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEA1381D-6EAC-41C3-9131-5F2E2B2B96C7@thelastpickle.com>
References: <372132B6-F983-4573-902F-232382DD8520@broodax.net>
To: user@cassandra.apache.org

You cannot do that in a single query.=20

The order of columns in output is the order they are stored in. And the =
API can only return a contiguous range of columns. =20

In this case I would get the larger slice and then discard columns =
client side. Or build a second row that has the order of the columns =
reversed so you can select from (0, null) to (2, null).

=
http://pycassa.github.com/pycassa/assorted/composite_types.html?#fetching-=
compositetype-data

Hope that helps.=20

-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 15/08/2012, at 4:10 PM, David Turnbull <david@broodax.net> wrote:

> Hi, I have a CF with a composite type (LongType, IntegerType) with =
some data like this:
>=20
> RowKey: hihi
> =3D> (column=3D1000:1, value=3D616263)
> =3D> (column=3D1000:2, value=3D6465)
> =3D> (column=3D1000:3, value=3D66)
> =3D> (column=3D1000:4, value=3D6768)
> =3D> (column=3D2000:1, value=3D616263)
> =3D> (column=3D2000:2, value=3D6465)
> =3D> (column=3D2000:3, value=3D66)
> =3D> (column=3D2000:4, value=3D6768)
>=20
> I want to query from (1000,0 to 2000,2) such that I get 1000:1, =
1000:2, 2000:1 and 2000:2 back.
> Is this possible?
>=20
> In pycassa, I can do cf.get('hihi', column_start=3D(1000,0), =
column_finish=3D(2000,2) but that gives me 1000:1-4 and 2000:1-2.
> Specifying a limit of 2 columns for the query just applies to the =
total results, i.e. only 1000:1 and 1000:2.
>=20
> I could specify the composite columns fully in the query, but I'm =
hoping to query over at least 300 columns, which seems bad.
>=20