> The kernel adds the string as an esp filter parameter and that doesn’t > work.
Sorry for leading you down the garden path here. pre 2.18 there's a lot of confusion around filters. An attempt (still not yet committed into 2.18) to solve it is discussed at (under "Fielded clause (& Custom) filters"): http://sesat.no/new-design-proposal-for-searchcommand-and-abstractsearchcommand.html#NewdesignproposalforSearchCommandandAbstractSearchCommand-Fieldedclause%2528%2526Custom%2529filters In the meantime add (something like) to your QueryTransfomer: {code} /** @deprecated temp solution before 2.18. only works when last in the query-transformer list. **/ public String getTransformedQuery(){ return super.getTransformedQuery() + ' ' + getFilter(context.getDataModel().getParameters()); } {code} Hope that helps out. (It will mean that the filter is also added to the BaseParameter.FILTER but i gather fast just ignores it here). If you could shed light on what you'd expect, or any possible solutions, on a new filter model in 2.18 that would be greatly appreciated. ~mck -- "The rainbow would not be without first the rain." D Donche Jr | semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
