Thanks for the guidance. I have a reasonable "middle ground" blend of
client-side and server side tweaks working now. In solr I copied my field
into a duplicate field sans folding filters, so that I essentially have
"myfield_raw" and "myfield_analyzed". Then on the client side include both
these
Thanks Erick, indeed your hunch is correct, it's the analyzing filters that
facet.prefix seems to bypass, and getting rid of my
ASCIIFoldingFilterFactory and MappingCharFilterFactory make it work ok.
The problem is I need those filters... otherwise how should I create facets
which match against bo
I'm finding that the facet.prefix query parameter does not seem to support
international characters, regardless of url encoding. All the other
parameters work fine, but that one seems unique in this respect.
For example with this data:
François Nédélec
*These queries produce relevant facets:*
Yes your assumptions are correct. I have built the suggester and it works
fine without the cfq.
These queries work:
/autocomplete?suggest.q=mexican&wt=json
/select?indent=on&q=+isoDateTime:[2016-05-16T0:0:0.0Z%20TO%20*]&wt=json
This one does not:
/autocomplete?suggest.q=mexican&suggest.
I'd like to use a date (TrieDate) for the contextField in my SuggestComponent
with an AnalyzingInfixLookupFactory. Basically am trying to narrow my
suggestions by a relevant date range, something like
suggest.cfq=[2017-05-15T0:0:0.0Z TO *]
Doesn't seem to work, so before trying further I wondered
