Hey,
we have multiple documents that are matches for the query in question
("name:hubwagen"). Thing is, some of the documents only contain the
query, while others match 100% in the "name" field:
Hochhubwagen
5.9861565
Hubwagen
5.9861565
The debug looks like this (for the first and
Hey,
I'm playing around with the suggester component, and it works perfectly
as described: Suggestions for 'logitech mouse' include 'logitech mouse
g500' and 'logitech mouse gaming'.
However, when the words in the record supplying the suggester do not
follow each other as in the search terms,
God damn. Thank you.
*ashamed*
Am 30.06.2015 00:21 schrieb Erick Erickson:
Try not putting it in double quotes?
Best,
Erick
On Mon, Jun 29, 2015 at 12:22 PM, Thomas Michael Engelke
thomas.enge...@posteo.de wrote:
A friend and I are trying to develop some software using Solr
A friend and I are trying to develop some software using Solr in the
background, and with that comes alot of changes. We're used to older
versions (4.3 and below). We especially have problems with the
autosuggest feature.
This is the field definition (schema.xml) for our autosuggest field:
Hey,
in german, you can string most nouns together by using hyphens, like
this:
Industrie = industry
Anhänger = trailer
Industrie-Anhänger = trailer for industrial use
Here [1], you can see me querying Industrieanhänger from the name
field (name:Industrieanhänger), to make sure the index
AM, Thomas Michael Engelke wrote:
Hey, in german, you can string most nouns together by using hyphens, like
this: Industrie = industry Anhänger = trailer Industrie- Anhänger = trailer
for industrial use Here [1[1]], you can see me querying Industrieanhänger
from the name field
I have Solr as the backend to an ECommerce solution where the fields can
be configured to be searchable, which generates a schema.xml and loads
it into Solr.
Now we also allow to configure Solr search weight per field to affect
queries, so my queries usually look something like this:
Thomas Michael Engelke:
I'm toying around with the suggester component, like described here:
http://www.andornot.com/blog/post/Advanced-autocomplete-with-Solr-Ngrams-and-Twitters-typeaheadjs.aspx
[1]
So I made 4 fields:
field name=text_suggest type=text_suggest indexed=true stored=true
Like in this article
(http://www.andornot.com/blog/post/Advanced-autocomplete-with-Solr-Ngrams-and-Twitters-typeaheadjs.aspx),
I am using multiple fields to generate different options for an
autosuggest functionality:
- First, the whole field (top priority)
- Then, the whole field as
this is basically
how all the Suggester implementations are designed to work already; are you
using one of those, or are you using the TermsComponent, or something else?
-Mike
On 11/10/14 2:54 AM, Thomas Michael Engelke wrote:
We're using Solr as a backend for an ECommerce site/system
I'm toying around with the suggester component, like described here:
http://www.andornot.com/blog/post/Advanced-autocomplete-with-Solr-Ngrams-and-Twitters-typeaheadjs.aspx
So I made 4 fields:
field name=text_suggest type=text_suggest indexed=true
stored=true multiValued=true /
copyField
We're using Solr as a backend for an ECommerce site/system. The Solr
index stores products with selected attributes, as well as a dedicated
field for autocomplete suggestions (Done via AJAX request when typing in
the search box without pressing return).
The autosuggest field is supplied by
We've moved from an asterisk based autosuggest functionality
(searchterm*) to a version using a special field called autosuggest,
filled via copyField directives. The field definition:
fieldType name=autosuggest class=solr.TextField
positionIncrementGap=100
:
On 7 October 2014 08:25, Thomas Michael Engelke
thomas.enge...@posteo.de wrote:
So the culprit is the asterisk at the end. As far as we can read from
the docs, an asterisk is just 0 or more characters, which means that
the literal word in front of the asterisk should match the query.
Not quite
I have a problem with a stemmed german field. The field definition:
field name=description type=text_splitting indexed=true
stored=true required=false multiValued=false/
...
fieldType name=text_splitting class=solr.TextField
positionIncrementGap=100 autoGeneratePhraseQueries=true
analyzer
spellcheck.alternativeTermCount to a
non-zero value (try maybe 5).
See
http://wiki.apache.org/solr/SpellCheckComponent#spellcheck.alternativeTermCount
[1] and following sections.
James Dyer
Ingram Content Group
(615) 213-4311
-Original Message-
From: Thomas Michael
Engelke
Hi,
I'm experimenting with the Spellcheck component and have therefor
used the example configuration for spell checking to try things out. My
solrconfig.xml looks like this:
searchComponent name=spellcheck
class=solr.SpellCheckComponent
str
name=queryAnalyzerFieldTypespell/str
!-- Multiple
I'm in the process of incorporating Solr spellchecking in our product.
For that, I've created a new field:
field name=spell type=spell
indexed=true stored=true required=false multiValued=false/
copyField source=name dest=spell maxChars=3 /
And in the
fieldType definitions:
fieldType
Ahmet Arslan:
Hi,
Please see :
https://issues.apache.org/jira/browse/SOLR-3925 [1]
Ahmet
On
Wednesday, July 30, 2014 2:39 PM, Thomas Michael Engelke
thomas.enge...@posteo.de wrote:
Hi,
an example. We have 2
records with this data in the same field
(description):
1:
Lufthutze vor
Hi,
an example. We have 2 records with this data in the same field
(description):
1: Lufthutze vor Kühler Bj 62-65, DS
2: Kühler HY im
Austausch, Altteilpfand 250 Euro
A search with the parameters
'description:Kühler' does provide this debug:
2.3234584 = (MATCH)
weight(description:kühler in
need to be slightly asymmetric.
-- Jack Krupansky
-Original Message- From: Thomas Michael Engelke
Sent: Thursday, January 30, 2014 2:16 AM
To: solr-user@lucene.apache.org
Subject: Re: Not finding part of fulltext field when word ends in dot
I'm not sure I got my problem across
Hello everybody,
we have a legacy solr installation in version 3.6.0.1. One of the indices
defines a field named content as a fulltext field where a product
description will reside. One of the records indexed contains the following
data (excerpt):
z. B. in der Serie 26KA.
I had the problem that
/
/analyzer
/fieldType
Thank you for taking a look.
2014-01-29 Jack Krupansky j...@basetechnology.com
What field type and analyzer/tokenizer are you using?
-- Jack Krupansky
-Original Message- From: Thomas Michael Engelke Sent: Wednesday,
January 29, 2014 10:45 AM To: solr
subtle word delimiter
filter changes between 3.x and 4.x.
Read:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201202.mbox/%
3CC0551C512C863540BC59694A118452AA0764A434@ITS-EMBX-03.
adsroot.itcs.umich.edu%3E
-Original Message- From: Thomas Michael Engelke
Sent: Wednesday
24 matches
Mail list logo
