Re: Applying Tokenizers and Filters to CopyFields

Glad it worked out... Looking back, I can't believe I didn't mention adding &debug=query to the URL. That would have shown you exactly what the parsed query looked like and you'd have seen right off that it wasn't searching against the field you thought it was. It's one of the first things I do wh

Re: Applying Tokenizers and Filters to CopyFields

Glad you are sorted out! Michael Della Bitta Senior Software Engineer o: +1 646 532 3062 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions | g+: plus.google.com/appinions

Re: Applying Tokenizers and Filters to CopyFields

Thanks so much, Erick and Michael, for all the additional explanation. The crucial information in the end turned out to be the one about the Default Search Field („df“). In solrconfig.xml this parameter was to point to the original text, which is why the expanded queries didn’t work. When I set

Re: Applying Tokenizers and Filters to CopyFields

Martin: Perhaps this would help indexed=true, stored=true field can be searched. The raw input (not analyzed in any way) can be shown to the user in the results list. indexed=true, stored=false field can be searched. However, the field can't be returned in the results list with the document. ind

Re: Applying Tokenizers and Filters to CopyFields

I agree the terminology is possibly a little confusing. Stored refers to values that are stored verbatim. You can retrieve them verbatim. Analysis does not affect stored values. Indexed values are tokenized/transformed and stored inverted. You can't recover the literal analyzed version (at least,

Re: Applying Tokenizers and Filters to CopyFields

Thanks a lot, Michael. See replies below. > Am 25.03.2015 um 21:41 schrieb Michael Della Bitta > : > > Two other things I noticed: > > 1. You probably don't want to store your copyFields. That's literally going > to be the same information each time. OK, got it. I have set the targets of the

Re: Applying Tokenizers and Filters to CopyFields

Thanks a lot, Ahmet. I’ve just read up on this query field parameter and it sounds good. Since the field contents are currently all identical, I can’t really test it, yet. Cheers, Martin > Am 25.03.2015 um 21:27 schrieb Ahmet Arslan : > > Hi Martin, > > fq means filter query. May be yo

Re: Applying Tokenizers and Filters to CopyFields

Two other things I noticed: 1. You probably don't want to store your copyFields. That's literally going to be the same information each time. 2. Your expectation "the pre-processed version of the text is added to the index" may be incorrect. Anything done in sections actually happens at query ti

Re: Applying Tokenizers and Filters to CopyFields

Hi Martin, fq means filter query. May be you want to use qf (query fields) parameter of edismax? On Wednesday, March 25, 2015 9:23 PM, Martin Wunderlich wrote: Hi all, I am wondering what the process is for applying Tokenizers and Filter (as defined in the FieldType definition) to field c