Riak To Support Secondary Indices

#1

Post by devpotato » Mon, Apr 25, 2011, 7:02 PM UTC

With Secondary Indices, users can tag their data with values, and can later query across their tagged data with simple SQL-style queries.

The following query, for example, will select the first 20 keys tagged with country of ‘Germany’ and category of ‘bread’, ‘sausage’, or ‘beer’, sorted by category and name:

FROM food WHERE country_id='Germany' AND category_id IN ('bread', 'sausage', 'beer') SORT BY category_id ASC, name_txt ASC SLICE 1 TO 20

Riak To Support Secondary Indices
oscon.com

Re: Riak To Support Secondary Indices

#2

Post by [deleted] » Mon, Apr 25, 2011, 7:20 PM UTC

[deleted]

Re: Riak To Support Secondary Indices

#3

Post by devpotato » Mon, Apr 25, 2011, 7:21 PM UTC

I haven't seen anything announced on Basho's website either. The talk abstract describes the talk as being the "unveiling" of secondary indices so it does seem like July is the release date.

Re: Riak To Support Secondary Indices

#4

Post by bfrog » Mon, Apr 25, 2011, 7:50 PM UTC

This could make riak actually useful to the masses as a fine database! Certainly one of my biggest beefs with riak was the overly difficult interface it has and its lack of secondary indexes.

The choice of protocol buffers as the serialization format is also kind of weak imho. There are some really piss poor protobuf implementations that are slower than serializing to xml or json. The python version especially comes to mind.

Re: Riak To Support Secondary Indices

#5

Post by RKlophaus » Mon, Apr 25, 2011, 7:51 PM UTC

The title should read 'Riak will support Secondary Indices.' As an open source company, we strive for transparent engineering; this is intended as a preview of some upcoming functionality. We haven't set a release date yet.

Just want to properly set expectations.

That said, we appreciate the interest and attention. :)

Re: Riak To Support Secondary Indices

#6

Post by bradfordw » Mon, Apr 25, 2011, 7:58 PM UTC

bfrog wrote: post #4

This could make riak actually useful to the masses as a fine database! Certainly one of my biggest beefs with riak was the overly difficult interface it has and its lack of secondary indexes. The choice of protocol buffers as the serialization format is also kind of weak imho. There are some really piss poor protobuf implementations that are slower than serializing to xml or json. The python version especially comes…

Sorry, I'm going to make an assumption that by interface difficulty you mean it's ability to be queried (map reduce only + lucene {optional})? Also, nothing forces you to use protobuffs, you can tell riak what (via the content type of an http header) what your data is and get it back as such. I don't see that as a weakness.

Re: Riak To Support Secondary Indices

#7

Post by kungfooguru » Mon, Apr 25, 2011, 11:48 PM UTC

RKlophaus wrote: post #5

The title should read 'Riak will support Secondary Indices.' As an open source company, we strive for transparent engineering; this is intended as a preview of some upcoming functionality. We haven't set a release date yet. Just want to properly set expectations. That said, we appreciate the interest and attention. :)

Will this, unlike Riak Search, provide the same guarantees about your data as the normal operations?

Re: Riak To Support Secondary Indices

#8

Post by drkrab » Tue, Apr 26, 2011, 11:39 AM UTC

The link seems to have dissolved; now redirecting to the front page of oscon.

Re: Riak To Support Secondary Indices

#9

Post by seancribbs » Tue, Apr 26, 2011, 3:53 PM UTC

kungfooguru wrote: post #7

RKlophaus wrote: post #5

The title should read 'Riak will support Secondary Indices.' As an open source company, we strive for transparent engineering; this is intended as a preview of some upcoming functionality. We haven't set a release date yet. Just want to properly set expectations. That said, we appreciate the interest and attention. :)

Will this, unlike Riak Search, provide the same guarantees about your data as the normal operations?

The design of secondary indexes is much simpler, more tightly integrated, and more transparent than Riak Search. It will feel more like part of the same datastore, rather than something you have to deal with on the side.