We are on GeoMesa 1.2.0 on top of
accumulo 1.6 with GeoServer 2.8.1. We started
experiencing issues combining complex cql quleries through
GeoServer for sure once we started applying more attribute
indexes on our data.
What seems to break down was when we
did multiple IN or = cql queries through one geoserver
call to the geomesa stack. Generic examples of what I’m
talking about that could fail would be against a column
defined as a String (I’ll call it Keyword) with index=full
with the cql looking something like the following 2
examples:
1. (Keyword
IN (‘test, ‘foo’))
2. ((Keyword
= ‘test’) OR (Keyword = ‘foo’))
If each was queried separately through
geoserver for the certain bounding box it works. But as
soon as we combine each working IN/equal match together
with the same bounding box it returns no matches via the
GeoServer GetMap call.
Also on the same dataset a query that
could succeed was something like:
((Keyword LIKE ‘foo%’) OR (Keyword IN
(‘test’))
I knew I did combine other queries so I
backed it off to a simple test dataset where I had not
indexed any additional attribute columns. So when I did
similar string tests like the 2 that failed above, they
worked against a non-indexed string attribute column. I
had no issues combining cql on admittedly non-indexed
Double columns. Unclear if I indexed them if I would
experience similar combined CQL issues.
Is there a known issue doing a
combined/multiple IN matches or = matches on an indexed
string attribute column?
Is there further things that anyone can
suggest I look at to determine why a multi IN clause or =
clause fails on an indexed string attribute column?
Thanks,
Diane Griffith