Sylvain Lebresne created CASSANDRA-11213:
--------------------------------------------
Summary: Improve ClusteringPrefix hierarchy
Key: CASSANDRA-11213
URL: https://issues.apache.org/jira/browse/CASSANDRA-11213
Project: Cassandra
Issue Type: Improvement
Reporter: Sylvain Lebresne
Fix For: 3.x
As noted by [~blambov] on CASSANDRA-11158, having {{RangeTombstone.Bound}} be a
subclass of {{Slice.Bound}} is somewhat inconsistent. I'd argue in fact that
conceptually neither should really be a subclass of the other as none is a
special case of the other and they are use in strictly non-overlapping places
({{Slice.Bound}} is for slices which are used for selecting data while
{{RangeTombstone.Bound}} is for range tombstone which actually represent some
type of data).
We should figure out a cleaner hierarchy of this, which probably mean slightly
changing the {{ClusteringPrefix}} hierarchy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
