Hello,
Our attribute indices don't store null values, so if you query for
"is null" it's going to end up doing a full table scan, which can
take a while. That said, it should return eventually. If you have
enabled query timeouts or blocked full table scans, that may be
preventing a result.
Can you enable explain logging, and reply back with the results?
https://www.geomesa.org/documentation/user/geoserver.html#logging-explain-query-planning
Thanks,
Emilio
On 1/3/19 3:06 PM, BKRuns26.2 wrote:
We are running into an issue of not being able to
filter null values on Indexed attributes.
We added a set of data that has several indexed attributes
(full indexes) for improved query performance that sometimes
contain null values. Filtering on the attributes via GeoServer
works fine unless we are trying to filter for all values that
are null. The standard GeoServer syntax of "is null" never
returns an empty feature collection yet we know null values
exist. No errors appear in the GeoServer log. If we filter
"is not null" it returns only values that aren't null so that
seems to work. Just the is null does not work.
Thanks,
Brad
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users
|
