[
https://issues.apache.org/jira/browse/CASSANDRA-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-3657:
----------------------------------------
Attachment: 0001-Allow-compatible-comparator-changes.patch
Attached patch that allows some valid comparator change. In addition to allow
adding new component for both CompositeType and DynamicCompositeType, it allows
to switch from AsciiType and UTF8Type to BytesType and from AsciiType to
UTF8Type (but I can remove that last part if someone don't feel good about it
for some reason, I just felt there is no real reason to not allow them).
> Allow extending CompositeType comparator
> ----------------------------------------
>
> Key: CASSANDRA-3657
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3657
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Affects Versions: 0.8.1
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Fix For: 1.1
>
> Attachments: 0001-Allow-compatible-comparator-changes.patch
>
>
> Quoting Sylvain from CASSANDRA-2474,
> bq. if you declare a comparator like CompositeType(IntType, UUIDType,
> UTF8Type), you can have columns that have only some prefix of the component
> (typically '42:92d21d0a-d6cb-437c-9d3f-b67aa733a19f' is a valid column name
> for that comparator), and as a consequence it would be possible to allow
> 'extend' the preceding comparator to say CompositeType(IntType, UUIDType,
> UTF8Type, IntType)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
