[
https://issues.apache.org/jira/browse/CASSANDRA-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039250#comment-14039250
]
Benedict commented on CASSANDRA-6917:
-------------------------------------
My main goal with enums is only uniquely representing a string value
efficiently. Supporting custom orderings on the data might be a possibility for
enums defined _up front_, however in this case I want to support denormalising
arbitrary string data, the universe of which could be moderately large
(certainly 100k+) and is not necessarily known in advance. An enum that must be
defined up front with a predetermined ordering is frankly just as easy to
implement client-side, so whilst it might be a nice feature to support
eventually, I consider it out of scope for this ticket, and I think
guaranteeing any specific order may be undesirable for write performance.
> 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
> 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
(v6.2#6252)
