You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2020/01/10 17:48:00 UTC
[jira] [Commented] (CASSANDRA-15498) Empty clustering instead of
Clustering.EMPTY
[ https://issues.apache.org/jira/browse/CASSANDRA-15498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013092#comment-17013092 ]
Ekaterina Dimitrova commented on CASSANDRA-15498:
-------------------------------------------------
Patch for trunk added [here|https://github.com/ekaterinadimitrova2/cassandra/tree/13595-continue].
Pull request ready for review:
[here|https://github.com/ekaterinadimitrova2/cassandra/pull/12]
> Empty clustering instead of Clustering.EMPTY
> --------------------------------------------
>
> Key: CASSANDRA-15498
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15498
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.x
>
>
> It seems that there are several ways to produce an empty clustering (with Kind.CLUSTERING) without using Clustering.EMPTY. They can be produced when copying another empty clustering (such as Clustering.EMPTY) , and also during deserialization when calling to Clustering.make
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org