[
https://issues.apache.org/jira/browse/CASSANDRA-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920350#action_12920350
]
Pavel Yaskevich commented on CASSANDRA-1603:
--------------------------------------------
If there were data before this kind of "typed" set it will be stored using
default CF validator which is BytesType (if column specific validator was not
set) or even column specific validator will be used. So if you "get" it will
just use default CF or column validator (is previously set) to covert stored
data into string (.getString())...
> 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.
