Re-enable (for now) the addition of ALLOW FILTERING to SELECT statements that include a filter column indexed by a non-standard index type (e.g. SASI, Lucene, etc.) as that's required and mysterious to end users.

This commit is contained in:
Greg Burd 2017-11-02 15:05:43 -04:00
parent 377191f12a
commit e4cda1a268

View file

@ -246,7 +246,7 @@ public final class SelectOperation<E> extends AbstractFilterStreamOperation<E, S
+ entity.getMappingInterface() + " or " + prop.getEntity().getMappingInterface());
}
// TODO(gburd): writeTime and ttl will be useful on merge() but cause object
// TODO(gburd): writeTime and ttl will be useful on merge() but cause object
// identity to fail.
if (false && cached) {
switch (prop.getProperty().getColumnType()) {
@ -289,7 +289,10 @@ public final class SelectOperation<E> extends AbstractFilterStreamOperation<E, S
for (Filter<?> filter : filters.values()) {
where.and(filter.getClause(sessionOps.getValuePreparer()));
}
if (filter.getNode().getProperty().caseSensitiveIndex()) {
allowFiltering = true;
}
}
}
if (ifFilters != null && !ifFilters.isEmpty()) {