[
https://issues.apache.org/jira/browse/CASSANDRA-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1603:
--------------------------------------
Attachment: 1603-v2.txt
updated to have getFormatTypeForColumn support Function names.
still needs to allow fixing errors -- if i set type long for instance but that
turns out to not be the kind of data that is in the column i need to be able to
override that later. i.e. we need to handle overriding when
hasValueValidator(columnNameInBytes, metadata) is true.
> 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
>
> Attachments: 1603-v2.txt, CASSANDRA-1603.patch
>
>
> 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.
