2010/2/4 Ted Zlatanov <t...@lifelogs.com>: > JE> The mask check needs to be done in the Slice Filter, not SP. > > Sorry, I don't know what you mean. Are you referring to > o.a.c.db.filter.SliceQueryFilter? So I'd just add an extra parameter to > the constructor and change the matching logic?
Right, but make it optional. > JE> Is this actually powerful enough to solve a real problem for you? > > Yes! OR+AND are exactly what I need. > > One specific situation: a supercolumn holds byte[] keys representing > network addresses (IPv4, IPv6, and Infiniband). I want to do efficient > queries across them by various netmasks; the netmasks are not trivial > and need the OR+AND structure. Right now I do it all on the client > side. I can't break things down by key or by supercolumn further > because I already use the supercolumn as a time (Long) index and the key > represents the specific colo. All right, let's give it a try.
