You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 06:06:01 UTC

[jira] [Updated] (CASSANDRA-6917) enum data type

     [ https://issues.apache.org/jira/browse/CASSANDRA-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

C. Scott Andreas updated CASSANDRA-6917:
----------------------------------------
    Component/s: CQL

> enum data type
> --------------
>
>                 Key: CASSANDRA-6917
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6917
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Benedict
>            Priority: Minor
>              Labels: performance
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org