You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2010/10/12 20:05:39 UTC

[jira] Commented: (CASSANDRA-1603) cli: allow entering binary data to columns with no metadata

    [ https://issues.apache.org/jira/browse/CASSANDRA-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920286#action_12920286 ] 

Pavel Yaskevich commented on CASSANDRA-1603:
--------------------------------------------

What if we make a function for each of the marshal types, e.g. long(), integer(), timeuuid() etc. However, we also dynamically change the column definition according to an assigned value. The reason being, we can know who is who e.g. :

1). column CF['hello'] does not have validation_class in column_metadata
2). {code}set CF['hello'] = integer(1039459847598){/code}
3). according to the function we convert the value to the right type and create/edit ColumnDef with right validation_class then set a value to the column
4). {code}get CF['hello']{/code} without problem we can covert the value according to the validation_class set on the previous step...

What do you think? Am I misunderstanding anything here?

> cli: allow entering binary data to columns with no metadata
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-1603
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1603
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>             Fix For: 0.7.0
>
>
> CASSANDRA-1578 adds support for when we have metadata for the column in the schema, but we should also allow manually turning a given string into a binary format.
> one option would be to allow something like
> {code}
> set CF[column]=timeuuid(12345678-1234-5678-1234-567812345678)
> {code}
> but this only allows data entry, and would not help when doing gets.
> maybe adding a cli command "assume column family with ..." would be best, allowing the operator to create local metadata that unlike "update columnfamily" doesn't get sent to the server.  (saving the local metadata between cli sessions would be good.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.