-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change search indexes to Haystack #280
Conversation
|
||
text = indexes.CharField(document=True) | ||
|
||
from wirecloud.commons.haystack_backends.solr_backend import GroupedSolrSearchBackend |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PEP-8 recommends that:
Imports are always put at the top of the file, just after any module comments and docstrings, and before module globals and constants.
What is the reason to import GroupedSolrSearchBackend
within the CatalogueResourceIndex
class definition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, it should be at the top.
Currently, its there as a placeholder while we look for a better solution that does not require to use a different field depending on the searching back-end.
Changes all indexes to use Haystack in order to support multiple search backends.
Haystack does not support grouping, so it has to be added. This is used for
catalogueresource
queries