Databases
StackOverflow2013
Postsdbo
POSolr search results with Django REST Framework
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSolr search results with Django REST Framework
    primarykey
    data
    text
    <p>I'm using <a href="http://django-rest-framework.org/" rel="nofollow">Django REST Framework</a> for our web API and <a href="http://lucene.apache.org/solr/" rel="nofollow">Solr</a> to power a search. Currenlty, in a subclass of <code>ListAPIView</code>, I override <code>get_queryset()</code> to get a <code>QuerySet</code> with the Solr search results:</p> <pre><code>class ClipList(generics.ListAPIView): """ List all Clips. Permissions: IsAuthenticatedOrReadOnly Parameters: query -- Search for Clips. EX: clips/?query=aaron%20rodgers """ model = Clip serializer_class = ClipSerializer permission_classes = (permissions.IsAuthenticatedOrReadOnly,) def get_queryset(self): params = request.GET query = params.get('query', None) queryset = Clip.objects.all() if query is not None: conn = solr.Solr(settings.SOLR_URL) sh = solr.SearchHandler(conn, "/select") response = sh(query) ids = [] for result in response.results: ids.append(result['id']) # filter the initial queryset based on the Clip identifiers from the Solr response # PROBLEM: This does not preserve the order of the results as it equates to # `SELECT * FROM clips WHERE id in (75, 89, 106, 45)`. # SQL is not guaranteed to return the results in the same order used in the WHERE clause. # There is no way (that I'm aware of) to do this in SQL. queryset = queryset.filter(pk__in=ids) return queryset </code></pre> <p>However, as explained in the comments, this does not preserve the order of the results. I realize I could make a Python set of Clip objects, but I would then lose the lazy-evaluation of Django <code>QuerySet</code> and the results are likely to be large and will be paginated.</p> <p>I looked into <a href="http://haystacksearch.org/" rel="nofollow">Haystack</a>, and my understanding is that the code above using Haystack would look like:</p> <pre><code> def get_queryset(self): params = self.request.GET query = params.get('query', None) search_queryset = SearchQuerySet().filter(content=query) return search_queryset </code></pre> <p>This is super simple and will maintain the order of the results, but Django REST Framework does not serialize <a href="http://django-haystack.readthedocs.org/en/latest/searchqueryset_api.html#ref-searchqueryset-api" rel="nofollow"><code>SearchQuerySets</code></a>.</p> <p>Is there a method in REST Framework that I can override that would allow for the serialization of <code>SearchQuerySets</code>? Or is there a way to maintain the ranked results order without using Haystack or Python sets?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShamsterdam
    1. UShamsterdam
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSolr search results with Django REST Framework
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSolr search results with Django REST Framework
      1. USallcaps
      1. VTFavorite
    3. VO
      singulars
      1. POSolr search results with Django REST Framework
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you just create your own serializer and add it to `serializer_class` instead of `ClipSerializer`?
      singulars
      1. POSolr search results with Django REST Framework
      1. USmariodev
    2. CODid you resolve this? I'm very interested in solving this right now because querying DB is very expensive at times where Solr would have no trouble performing the query at all.
      singulars
      1. POSolr search results with Django REST Framework
      1. USjooks
    3. COHey @jooks, we did resolve this by creating what we're calling `SearchListModelMixin` and using that in `SearchListAPIView` and SearchListCreateAPIView`. Essentially, you just add a `get_search_results` method to each view, similar to `get_queryset`. The key to the whole thing is a bit hacky though. We achieved pagination by mimicking Django page objects to provide the correct total result count. At some point, hopefully we will open source it. We tried to follow Django and Django REST Framework idioms as best we could.
      singulars
      1. POSolr search results with Django REST Framework
      1. UShamsterdam
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload