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 5th
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, no
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
> wrote:
>
>> A friend and I are trying to develop s
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:
.
used the analysis tab in the admin UI? You can type in
sentences for both index and query time and see how they would be
analysed by various fields/field types.
Once you have got index time and query time to result in the same tokens
at the end of the analysis chain, you should start seeing matches in
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 a
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:
spellch
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 EdgeNGram
2014 08:52 schrieb 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:
>
> multiValued="
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:
stored="true" multiValued="true" />
stored="true" multiValued="true" />
indexed="true" stored=
ces only tokens that are in the main index. I think 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 Mi
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 cop
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:
positionIncrementGap="100">
class=
afalovitch:
On 7 October 2014 08:25, Thomas Michael Engelke
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: http://wiki.
I have a problem with a stemmed german field. The field definition:
stored="true" required="false" multiValued="false"/>
...
positionIncrementGap="100" autoGeneratePhraseQueries="true">
words="stopwords.txt"/>
generateWordParts="1" generateNumberParts="1" catenateWords="1"
catenateN
ithin 2 edits of
"ichtscheiben" ? My guess is you probably don't, which would be why you
do not get spelling results in that case.
>
> Also, even if you do have
something within 2 edits, if "ichtscheiben" occurs in your index, by
default it won't try to correct it at
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:
spell
default
spell
solr.DirectSolrSpellChecker
internal
wordbreak
solr.WordBreakSolrSpellChecker
I'm in the process of incorporating Solr spellchecking in our product.
For that, I've created a new field:
And in the
fieldType definitions:
Then I feed the names of products into the corresponding
core. They can have a lot of words (examples):
door lock rear left
Door brake,
rmFreq=1.0
6.226491 = idf(docFreq=64, maxDocs=12099)
0.375 =
fieldNorm(doc=5754)
Am I using this feature wrong?
Am
30.07.2014 14:48 schrieb Ahmet Arslan:
> Hi,
>
> Please see :
https://issues.apache.org/jira/browse/SOLR-3925 [1]
>
> Ahmet
>
> On
Wednesday, July 30, 2014 2:39 PM
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 40
railing dot) to be in the index.
>
> It seems counter-intuitive, but the attributes of the index and query word
> delimiter filters need to be slightly asymmetric.
>
>
> -- Jack Krupansky
>
> -Original Message- From: Thomas Michael Engelke
> Sent: Thursday, Janua
There may have been some 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 M
you for taking a look.
2014-01-29 Jack Krupansky
> What field type and analyzer/tokenizer are you using?
>
> -- Jack Krupansky
>
> -Original Message----- From: Thomas Michael Engelke Sent: Wednesday,
> January
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 tha
24 matches
Mail list logo
