On Thu, Oct 7, 2010 at 6:25 PM, Jonathan Ellis <jbel...@gmail.com> wrote:
> On Thu, Oct 7, 2010 at 10:13 AM, Christian Decker > <decker.christ...@gmail.com> wrote: > > So basically my indices should work? Is there a simple way to check that, > so > > that we can exclude that? > > > > Are LTE working (or on the roadmap for the 0.7.0 release)? > > No, LT[E] is not on the roadmap for primary index clauses (GT[E] is, > for 0.7.1). So you would want to create an index with an inverted > comparator, to turn LTE into GTE. > Hm, sounds rather strange, but that would mean that I'd either be able to select GT[E] or LT[E], not combining both, right? So expressions like 123 < uid < 321 would be completely impossible. How would one proceed to create an index with an inverted comparator? I'd have to create my own Sub-Type on which I'd invert compare function. And I'd be able as stated above to select only in one direction? > > > Or does the EQ > > operator have to math anything or can I just add an EQ to a not existing > > value to get LTE working too? > > If you ask for EQ not-existing-value you will get no results back, of > course. -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com > By the way, I saw your commit earlier that allowed for dynamic index creation on existing CFs, it helped me create the indices, thanks :-)
