Niclas Hedhman a écrit : > On Tue, Oct 2, 2012 at 4:27 PM, Paul Merlin <[email protected]> wrote: >> - don't support MatchesSpecification as ElasticSearch don't support >> regex based queries/filters (yet, see the documentation) ; > Does this warrant us to take it out completely?? And perhaps add a > "post search filtering" mechanism instead? ElasticSearch will support regex filtering when lucene 4 will be out (currently at BETA stage).
If we need this beforehand we could implement a post search filtering but I'm afraid that it could be something terrible in many cases. First it will make the indexing-elasticsearch code complex whereas it's quite simple for now. Plus I only get hits (containing entities identities) from the ElasticSearch instance, not full states, so it would mean: - gathering hits from ElasticSearch - loading entities states from EntityStore - applying filter on Entities states I'm not sure it's a good idea :-) Another option would be to push ElasticSearch towards including RegexFilterBuilder before Lucene 4 as it's doable but will have "poor" performance because of the way Lucene 3 handle regex queries/filters. /Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
