Databases
StackOverflow2013
Postsdbo
PODjango haystack EdgeNgramField given different results than elasticsearch
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango haystack EdgeNgramField given different results than elasticsearch
    primarykey
    data
    text
    <p>I'm currently running haystack with an elasticsearch backend, and now I'm building an autocomplete for cities names. The problem is that SearchQuerySet is giving me different results, which from my perspective are wrong, than the same query executed directly in elasticsearch, which are for me the expected results. </p> <p>I'm using: Django 1.5.4, django-haystack 2.1.0, pyelasticsearch 0.6.1, elasticsearch 0.90.3</p> <p>Using the following example data:</p> <ul> <li>Midfield </li> <li>Midland City </li> <li>Midway </li> <li>Minor </li> <li>Minturn </li> <li>Miami Beach</li> </ul> <p>Using either </p> <pre><code>SearchQuerySet().models(Geoname).filter(name_auto='mid') or SearchQuerySet().models(Geoname).autocomplete(name_auto='mid') </code></pre> <p>The result returns always all the 6 names, including Min* and Mia*...however, querying elasticsearch directly returns the right data:</p> <pre><code>"query": { "filtered" : { "query" : { "match_all": {} }, "filter" : { "term": {"name_auto": "mid"} } } } { "took": 1, "timed_out": false, "_shards": { "total": 5, "successful": 5, "failed": 0 }, "hits": { "total": 3, "max_score": 1, "hits": [ { "_index": "haystack", "_type": "modelresult", "_id": "csi.geoname.4075977", "_score": 1, "_source": { "name_auto": "Midfield", } }, { "_index": "haystack", "_type": "modelresult", "_id": "csi.geoname.4075984", "_score": 1, "_source": { "name_auto": "Midland City", } }, { "_index": "haystack", "_type": "modelresult", "_id": "csi.geoname.4075989", "_score": 1, "_source": { "name_auto": "Midway", } } ] } } </code></pre> <p>The behavior is the same with different examples. My guess is that trough haystack the string it's being split and analyzed by all possible "min_gram" groups of characters and that's why it returns wrong results.</p> <p>I'm not sure if I am doing or understanding something wrong, and if is this how haystack is supposed to work, but I need that haystack results match the elasticsearch results.</p> <p>So, How can I fix the issue or make it works ?</p> <p>My summarized objects look as follow:</p> <p>Model:</p> <pre><code>class Geoname(models.Model): id = models.IntegerField(primary_key=True) name = models.CharField(max_length=255) </code></pre> <p>Index:</p> <pre><code>class GeonameIndex(indexes.SearchIndex, indexes.Indexable): text = indexes.CharField(document=True, use_template=True) name_auto = indexes.EdgeNgramField(model_attr='name') def get_model(self): return Geoname </code></pre> <p>Mapping:</p> <pre><code>modelresult: { _boost: { name: "boost", null_value: 1 }, properties: { django_ct: { type: "string" }, django_id: { type: "string" }, name_auto: { type: "string", store: true, term_vector: "with_positions_offsets", analyzer: "edgengram_analyzer" } } } </code></pre> <p>Thank you.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStufla
    1. UStufla
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango haystack EdgeNgramField given different results than elasticsearch
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango haystack EdgeNgramField given different results than elasticsearch
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODjango haystack EdgeNgramField given different results than elasticsearch
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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