[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    Re: Cassandra Views
From:       Sylvain Lebresne <sylvain () datastax ! com>
Date:       2014-10-13 9:35:34
Message-ID: CAKkz8Q2vkY7tYWQ-xdQAx6dDD2kB=oa6SVXkLVo83M+dz+kc+w () mail ! gmail ! com
[Download RAW message or body]


On Mon, Oct 13, 2014 at 7:15 AM, Jonathan Ellis <jbellis@gmail.com> wrote:

> On Mon, Oct 6, 2014 at 5:18 PM, Tilmann Rabl <tilmann.rabl@utoronto.ca>
> wrote:
>
> > Our old version has used CFMetaData.comparator.getString(Colum.name) to
> > get the name of a column (and the value) and that was then used to
> specify
> > column names in the view. We used CFMetaData.comparator.fromString to
> > generate the ByteBuffer representation.
> > It seems the new Composite representation should be able to do that in a
> > more efficient way (e.g., combine column names and keys), but I could not
> > figure out how to do it.
>

I'm not exactly sure what you mean by "combine column names and keys" tbh,
mind precising? I mean, you can get a ByteBuffer from a Composite through
the toByteBuffer() method, which would allows you to use
CFMetaData.comparator.getString as before, but I'm not sure this is what
you're asking for.


> That is a good question.  This was introduced in CASSANDRA-5147,


And by that you mean CASSANDRA-5417 :)


> and there's a number of examples in the tests where we converted from the
> old
> getString approach (e.g. Util.cellname methods) but in general I'm a little
> fuzzy on how this works.  Sylvain, do we have a writeup on this anywhere?
>

Well, the code is really the best of writeups :). But outside some comments
on the
ticket and the code/comments, no, we don't really have other write-ups on
this.

--
Sylvain


[prev in list] [next in list] [prev in thread] [next in thread]