Closed parasgithub closed 9 years ago
There's not much point in changing the analyzer on those fields because those fields are already, and purposefully, analyzer specific in Haystack.
If you want to use a different analyzer to do similar work, I'd recommend just specifying a new field using ConfigurableFieldMixin
.
The only time I can see this being a problem is if you have no control over what fields are used in the SearchIndex
class(es). If that is indeed a problem I'd consider a pull request to resolve the issue (see the contribution doc).
Why can we not change the analyzer for edge_ngram and ngram fields?