[
https://issues.apache.org/jira/browse/CASSANDRA-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-334:
-------------------------------------
Attachment: 334.patch
I don't think we should silently fall back to lexical comparison if the user
specifies time-based compares but then passes in something else by mistake.
Instead, we should reject the insert.
Alternative patch attached for comment.
> Temporally Ordered Sub columns in a SuperColumnFamily
> -----------------------------------------------------
>
> Key: CASSANDRA-334
> URL: https://issues.apache.org/jira/browse/CASSANDRA-334
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Michael Koziarski
> Attachments: 334.patch, cassandra-334-koz-first.diff
>
>
> Since the switch to typed column names and CompareSubcolumnsWith we no longer
> have a simple way to order entries in a super column / column family by their
> creation time. This makes things like 'timelines' harder to implement.
> After discussions on IRC / twitter it appears we could achieve this with a
> new comparator for UUIDTypes which checks their temporal order before just
> falling back on their lexical order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
