Re: Clustering key and secondary index behavior changed between 2.0.11 and 3.3.0

2016-04-05 Thread Sylvain Lebresne
I'm surprised this would have fall through the cracks but that certainly look like a regression (a bug). If you can reproduce on 3.0.4 (just to make sure we haven't fixed it recently), then please open a ticket in https://issues.apache.org/jira/browse/CASSANDRA/ with your repro steps. On Tue, Apr

Clustering key and secondary index behavior changed between 2.0.11 and 3.3.0

2016-04-05 Thread julien muller
Hello, I noticed the following change in behavior while migrating from 2.0.11: Elements of the clustering key seems to not be secondary indexable anymore. Anyone could give me an insight about this issue? Or point me to documents relative to this evolution? There is a sample table with some data: