[
https://issues.apache.org/jira/browse/CASSANDRA-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023142#comment-13023142
]
Sylvain Lebresne commented on CASSANDRA-2530:
---------------------------------------------
bq. My reasoning was more about a guaranteed length that was short. We plan to
put ENUMs into them in prepared statements. Again, selfishly, if we have a lot
of Float usage we really have a lot of numbers between 1-10 to store! So all
these volumes above are just more exaggerated in our need to store lots of
short numbers in an optimal width. But I do understand the variable integer
IntegerType could be used.
It think what you want to use is a BytesType with only one byte each time. The
only thing that you'll miss is that validate won't ensure you only have 1 byte
long inputs. However, for that kind of thing, I would be in favor of using
CASSANDRA-2355 and enriching BytesType so that you can write stuff like
BytesType(max_length=1). That's more flexible and avoid adding tons of new
classes.
> Additional AbstractType data type definitions to enrich CQL
> -----------------------------------------------------------
>
> Key: CASSANDRA-2530
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2530
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Rick Shaw
> Priority: Trivial
> Labels: cql
> Attachments: patch-to-add -5 -new-AbstractTypes-v2.txt, patch-to-add
> -5 -new-AbstractTypes-v3.txt, patch-to-add -5 -new-AbstractTypes.txt
>
>
> Provide 5 additional Datatypes: ByteType, DateType, BooleanType, FloatType,
> DoubleType.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
