Re: Solr Grouping and empty fields
Hi Oussama, If you have only a few distinct, unchanging values in the field that you group upon, you could implement a FilterQuery (query parameter "fq") and add it to the query, allowing all valid values, but not an empty field. For example: fq=my_grouping_string_field:( value_a OR value_b OR value_c OR value_d ) If you use SOLR 4.x, you should be able to group upon an integer field, allowing a range filter: (I still work with 3.6 which can only group on string fields, so i didnt test this one) fq=my_grouping_integer_field:[1 TO *] -- Johannes Rodenwald - Ursprüngliche Mail - Von: "Oussama Jilal" An: solr-user@lucene.apache.org Gesendet: Freitag, 22. Februar 2013 12:32:13 Betreff: Solr Grouping and empty fields Hi, I need to group some results in solr based on a field, but I don't want documents having that field empty to be grouped together, does anyone know how to achieve that ? -- Oussama Jilal
Re: Index-time synonyms and trailing wildcard issue
Hello Jack,
Thanks for your answer, it helped me gaining a deeper understandig what happens
at index time, and finding a solution myself:
It seems that putting the synonym filter in both filter chains (index and
query), setting expand="false", and putting the desired synonym first in the
row, does the trick:
Synonyms line (reversed order!):
orange, apfelsine
All documents containing "apfelsine" are now mapped to "orange", so there are
no more documets containing "apfelsine" that would match a wildcard-query for
"apfel*" ("Apfelsine" is a true synonym for "Orange" in german, meaning
"chinese apple". "Apfel" = apple, shouldnt match oranges).
Problem solved, thanks again for the help!
Johannes Rodenwald
- Ursprüngliche Mail -
Von: "Jack Krupansky"
An: solr-user@lucene.apache.org
Gesendet: Mittwoch, 13. Februar 2013 17:17:40
Betreff: Re: Index-time synonyms and trailing wildcard issue
By doing synonyms at index time, you cause "apfelsin" to be added to
documents that contain only "orang", so of course documents that previously
only contained "orang" will now match for "apfelsin" or any term query that
matches "apfelsin", such as a wildcard. At query time, Lucene cannot tell
whether your original document contained "apfelsin" or if "apfelsin" was
added when the document was indexed due to an index-time synonym.
Solution: Either disable index time synonyms, or have a parallel field (via
copyField) that does not have the index-time synonyms.
But... perhaps you should clarify what you really intend to happen with
these pseudo-synonyms.
-- Jack Krupansky
Index-time synonyms and trailing wildcard issue
Hi, I use Solr 3.6.0 with a synonym filter as the last filter at index time, using a list of stemmed terms. When i do a wildcard search that matches a part of an entry on the synonym list, the synonyms found are used by solr to generate the search results. I am trying to disable that behaviour, but with no success. Example: Stemmed synonyms: apfelsin, orang Search term: apfel* Matches: Apfelkuchen, Apfelsaft, Apfelsine... (good, i want these matches) Orange (bad, i dont want this match) My questions are: - Why does the synonym filter react on a wildcard query? For it is not a multiterm-aware component (see http://lucene.apache.org/solr/api-3_6_1/org/apache/solr/analysis/MultiTermAwareComponent.html) - How can i disable this behaviour, so that "Orange" is no longer returned by the query for "apfel*"? Regards, Johannes
