cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4212) COMPACT STORAGE should not require a value to be aliased
Date Thu, 03 May 2012 10:38:54 GMT


Sylvain Lebresne commented on CASSANDRA-4212:

First, I'm slightly confused by the patch with respect to the description of this ticket.
Are we talking about aliasing the underlying column "name" or "value". The description does
suggest the value (for which validation has been added by the 2nd patch of CASSANDRA-4185)
but the patch remove the validation for the name.

That being said, I'll assume you mean that the "value" shouldn't be required to be aliased,
because I can't make sense of it for the column name. And I'll also suspect you're talking
of the case where you're not interested by the column values and want them to always be empty.
If so, I could agree it may be worth supporting that, but we'd need to at least modify the
insertion to automatically use an EMPTY_BYTE_BUFFER for the value in that case, otherwise
there will be no way to insert data on such column family.

But the last thing adding to my confusion is that system.NodeIdInfo does store information
in the column values, so I'm not totally sure I understand the suggestion here.
> COMPACT STORAGE should not require a value to be aliased
> --------------------------------------------------------
>                 Key: CASSANDRA-4212
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>              Labels: cql3
>             Fix For: 1.1.1
>         Attachments: 4212.txt
> It's legitimate to only need the column name in a schema, e.g., system.NodeIdInfo.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message