Note that there are some explanatory texts on larger screens.

plurals
  1. POLucene Query (with shingles ? )
    primarykey
    data
    text
    <p>I have a Lucene Index containing documents like these : </p> <pre><code>_id | Name | Alternate Names | Population 123 Bosc de Planavilla (some names here in 5000 345 Planavilla other languages) 20000 456 Bosc de la Planassa 1000 567 Bosc de Plana en Blanca 100000 </code></pre> <p>What's the best Lucene query type I should use and how should I structure it considering I need the following : </p> <ol> <li><p>If a user queries for : "Italian Restaurant near Bosc de Planavilla" I want document with id 123 to be returned because its contains an exact match with the name of the doc.</p></li> <li><p>If a user queries for : "Italian Restaurant near Planavilla" I want document with id 345 because query contains an exact match AND it has the highest population.</p></li> <li><p>If a user queries for "Italian Restaurant near Bosc" I want 567 because query contains "Bosc" AND of the 3 "Bosc" it has the highest pop.</p></li> </ol> <p>there are probably many other use cases ... but you get the feeling of what i need ...</p> <p>What kind of query will do this form me ? Should I generate word N grams (shingles) and create an ORed boolean query using the shingles then apply custom scoring ? or will a regular phrase query will do ? I also saw DisjunctionMaxQuery but dont know if its what im looking for ... </p> <p>The idea, as you might have anderstood by now, is to find the exact Location a user implied in his query. From that I can start my Geo search and add some further querying around that. </p> <p>What's the best approach ?</p> <p>Thanks in advance .</p>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
 

Querying!

 
Guidance

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