Chris Adams
Chris Adams
See https://github.com/django-haystack/django-haystack/pull/1285 and https://github.com/django-haystack/django-haystack/issues/1041#issuecomment-149902911. If you have time to work on the backwards-compatibility issues, it would probably be better helping get one of those up to merge-ready status.
Looks like this branch could use an update for the collection name code and then the main blocker would be enabling tests.
It would probably be a good idea to add code to the Solr & ES backends to raise a `NotImplementedError` if `ANALYZER` is present until someone takes the time to...
Can you fix the tests on this so it passes?
This definitely looks like a good candidate for rebasing against the current branch and shipping.
`HAYSTACK_FUZZY_MAX_EXPANSIONS` is only supported by the ES backend currently so perhaps we should make that an option specific to that backend if nothing else supports it.
This ticket is pretty old – can someone confirm whether this is still relevant with the current haystack & ES client library?
This needs some description and passing tests
@maikthomas We really should have some tests before this could be merged. If this would be valuable to you, I would start by updating it against the current master branch...
Oddly, the whoosh backend was performing the check but not actually using `model_klass` anywhere in the method. Further investigation is needed…