cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6917) enum data type
Date Mon, 24 Mar 2014 19:36:43 GMT

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

Jonathan Ellis edited comment on CASSANDRA-6917 at 3/24/14 7:35 PM:
--------------------------------------------------------------------

see also CASSANDRA-4175


was (Author: jbellis):
see also CASSNADRA-4175

> enum data type
> --------------
>
>                 Key: CASSANDRA-6917
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6917
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Priority: Minor
>
> It seems like it would be useful to support an enum data type, that automatically converts
string data from the user into a fixed-width data type with guaranteed uniqueness across the
cluster. This data would be replicated to all nodes for lookup, but ideally would use only
the keyspace RF to determine nodes for coordinating quorum writes/consistency.
> This would not only permit improved local disk and inter-node network IO for symbology
information (e.g. stock tickers, ISINs, etc), but also potentially for column identifiers
also, which are currently stored as their full string representation.
> It should be possible then with later updates to propagate the enum map (lazily) to clients
through the native protocol, reducing network IO further.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message