Re: WordDelimiter in extended way.

got it, thank you -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: WordDelimiter in extended way.

On 10/23/2019 9:41 AM, servus01 wrote: Hey, thank you for helping me: Thanks in advanced for any help, really appriciate. <https://lucene.472066.n3.nabble.com/file/t494058/screenshot.jpg> <https://lucene.472066.n3.nabble.com/file/t494058/screenshot3.jpg> It is not the WordDeli

Re: WordDelimiter in extended way.

Hey, thank you for helping me: Thanks in advanced for any help, really appriciate. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.h

Re: WordDelimiter in extended way.

On 10/23/2019 7:43 AM, servus01 wrote: Now Solr behaves in such a way that on the one hand the hyphens which have a blank before and after are not indexed and also the search as soon as blank - blank is searched does not return any results. With the WordDelimiter I have already covered the cases

WordDelimiter in extended way.

d *mp4 - 2.* BL 2019-2020 1st matchday SV Wehen Wiesbaden vs. Karlsruher SC" Now Solr behaves in such a way that on the one hand the hyphens which have a blank before and after are not indexed and also the search as soon as blank - blank is searched does not return any results. With the

Re: WordDelimiter Works differently in solr3X vs SolrCloud..?

Thanks Ahmet, that works. - -goutham -- View this message in context: http://lucene.472066.n3.nabble.com/WordDelimiter-Works-differently-in-solr3X-vs-SolrCloud-tp4179647p4179662.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: WordDelimiter Works differently in solr3X vs SolrCloud..?

setting mentioned as above. -- View this message in context: http://lucene.472066.n3.nabble.com/WordDelimiter-Works-differently-in-solr3X-vs-SolrCloud-tp4179647.html Sent from the Solr - User mailing list archive at Nabble.com.

WordDelimiter Works differently in solr3X vs SolrCloud..?

tch when queried for “ipad2” with WDF setting mentioned as above. -- View this message in context: http://lucene.472066.n3.nabble.com/WordDelimiter-Works-differently-in-solr3X-vs-SolrCloud-tp4179647.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: WordDelimiter filter, expanding to multiple words, unexpected results

There are two approaches for the query “mixedCase” to match “mixed Case” in the original document. 1. Add an index time synonym. 2. Add a ShingleFilterFactory to the index analysis chain. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ On Dec 30, 2014, at 9:50 AM,

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 12/30/14 12:42 PM, Jonathan Rochkind wrote: On 12/30/14 12:35 PM, Walter Underwood wrote: You want preserveOriginal=“1”. You should only do this processing at index time. If I only do this processing at index time, then "mixedCase" at query time will no longer match "mixed Case" in the in

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 12/30/14 12:35 PM, Walter Underwood wrote: You want preserveOriginal=“1”. You should only do this processing at index time. If I only do this processing at index time, then "mixedCase" at query time will no longer match "mixed Case" in the index/source material. I think I'm having troubl

Re: WordDelimiter filter, expanding to multiple words, unexpected results

You want preserveOriginal=“1”. You should only do this processing at index time. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ On Dec 30, 2014, at 9:33 AM, Jonathan Rochkind wrote: > Okay, thanks. I'm not sure if it's my lack of understanding, but I feel like

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Okay, thanks. I'm not sure if it's my lack of understanding, but I feel like I'm having a very hard time getting straight answers out of you all, here. I want the query "mixedCase" to match both/either "mixed Case" and "mixedCase" in the index. What configuration of WDF at index/query time w

Re: WordDelimiter filter, expanding to multiple words, unexpected results

I do have a more thorough discussion of WDF in my Solr Deep Dive e-book: http://www.lulu.com/us/en/shop/jack-krupansky/solr-4x-deep-dive-early-access-release-7/ebook/product-21203548.html You're not "wrong" about anything here... you just need to accept that WDF is not magic and can't handle every

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 12/30/14 11:45 AM, Alexandre Rafalovitch wrote: On 30 December 2014 at 11:12, Jonathan Rochkind wrote: I'm a bit confused about what splitOnCaseChange combined with catenateWords is meant to do at all. It _is_ generating both the split and single-word tokens at query time Have you tried o

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 30 December 2014 at 11:12, Jonathan Rochkind wrote: > I'm a bit confused about what splitOnCaseChange combined with catenateWords > is meant to do at all. It _is_ generating both the split and single-word > tokens at query time Have you tried only having WDF during indexing with both options

Re: WordDelimiter filter, expanding to multiple words, unexpected results

I guess I don't understand what the four use cases are, or the three out of four use cases, or whatever. What the intended uses of the WDF are. Can you explain what the intended use of setting: generateWordParts="1" catenateWords="1" splitOnCaseChange="1" Is that supposed to do something usefu

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Right, that's what I meant by WDF not being "magic" - you can configure it to match any three out of four use cases as you choose, but there is no choice that matches all of the use cases. To be clear, this is not a "bug" in WDF, but simply a limitation. -- Jack Krupansky On Tue, Dec 30, 2014 a

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Thanks Erick! Yes, if I set splitOnCaseChange=0, then of course it'll work -- but then query for "mixedCase" will no longer also match "mixed Case". I think I want WDF to... kind of do all of the above. Specifically, I had thought that it would allow a query for "mixedCase" to match both/eit

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 29 December 2014 at 18:07, Jonathan Rochkind wrote: > I do not understand what separate query/index analysis you are suggesting to > accomplish what I wanted. I am sure you do know that, but just in case. At the moment, you have only one analyzer chain, so it applies at both index and query ti

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Jonathan: Well, it works if you set splitOnCaseChange="0" in just the query part of the analysis chain. I probably mislead you a bit months ago, WDFF is intended for this case iff you expect the case change to generate _tokens_ that are individually meaningful.. And unfortunately "significant" in

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 12/29/14 5:24 PM, Jack Krupansky wrote: WDF is powerful, but it is not magic. In general, the indexed data is expected to be clean while the query might be sloppy. You need to separate the index and query analyzers and they need to respect that distinction I do not understand what separate q

Re: WordDelimiter filter, expanding to multiple words, unexpected results

wrote: > Okay, some months later I've come back to this with an isolated reproduction > case. Thanks very much for any advice or debugging help you can give. > > The WordDelimiter filter is making a mixed-case query NOT match the > single-case source, when it ought to. > > I am

Re: WordDelimiter filter, expanding to multiple words, unexpected results

, Jonathan Rochkind wrote: > Okay, some months later I've come back to this with an isolated > reproduction case. Thanks very much for any advice or debugging help you > can give. > > The WordDelimiter filter is making a mixed-case query NOT match the > single-case source, whe

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Okay, some months later I've come back to this with an isolated reproduction case. Thanks very much for any advice or debugging help you can give. The WordDelimiter filter is making a mixed-case query NOT match the single-case source, when it ought to. I am in Solr 4.3 (sorry, that&#

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Jonathan: If at all possible, delete your collection/data directory (the whole directory, including data) between runs after you've changed your schema (at least any of your analysis that pertains to indexing). Mixing old and new schema definitions can add to the confusion! Good luck! Erick On W

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Thanks Erick and Diego. Yes, I noticed in my last message I'm not actually using defaults, not sure why I chose non-defaults originally. I still need to find time to make a smaller isolation/reproduction case, I'm getting confusing results that suggest some other part of my field def may be pe

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Although not a solution, this may help in trying to find the problem. In http://solr.pl/en/2010/08/16/what-is-schema-xml/ it says: "It is worth noting that there is an additional attribute for the text field type: autoGeneratePhraseQueries This attribute is responsible for telling filters h

Re: WordDelimiter filter, expanding to multiple words, unexpected results

What happens if you append &debug=query to your query? IOW, what does the _parsed_ query look like? Also note that the defaults for WDFF are _not_ identical. catenateWords and catenateNumbers are 1 in the index portion and 0 in the query section. Still, this shouldn't be a problem all other things

Re: WordDelimiter filter, expanding to multiple words, unexpected results

On 9/2/14 1:51 PM, Erick Erickson wrote: bq: In my actual index, query "MacBook" is matching ONLY "mac book", and not "macbook" I suspect your query parameters for WordDelimiterFilterFactory doesn't have catenate words set. What do you see when you enter these in both the index and query portio

Re: WordDelimiter filter, expanding to multiple words, unexpected results

ot > > "macbook". Which is unexpected. I indeed want it to match both. (I > realize > > I could make it match only 'macbook' by setting splitOnCaseChange=0 > and/or > > generateWordParts=0). > > > > It's possible this is happening as a

Re: WordDelimiter filter, expanding to multiple words, unexpected results

hange=0 and/or generateWordParts=0). It's possible this is happening as a side effect of other parts of my complex field definition, and I really do need to post hte whole thing and/or isolate it. But I wonder if there are known general problem cases that cause this kind of failure, or any kn

Re: WordDelimiter filter, expanding to multiple words, unexpected results

ate it. But I wonder if there are known general problem cases > that cause this kind of failure, or any known bugs in WordDelimiterFilter > (in Solr 4.3?) that cause this kind of failure. > > And I wonder if WordDelimiter filter spitting out the token "MacBook" with > posi

Re: WordDelimiter filter, expanding to multiple words, unexpected results

e, or any known bugs in WordDelimiterFilter (in Solr 4.3?) that cause this kind of failure. And I wonder if WordDelimiter filter spitting out the token "MacBook" with position "2" rather than "1" is expected, irrelevant, or possibly a relevant problem. Thanks agai

Re: WordDelimiter filter, expanding to multiple words, unexpected results

Hi Jonathan, Little confused by this line: > And, what I think it's trying to do, is match text indexed as "d elalain" as well as text indexed by "delalain". In this case, I don't know how WordDelimiterFilter will help, as you're likely tokenizing on spaces somewhere, and that input text has a s

WordDelimiter filter, expanding to multiple words, unexpected results

Hello, I'm running into a case where a query is not returning the results I expect, and I'm hoping someone can offer some explanation that might help me fine tune things or understand what's up. I am running Solr 4.3. My filter chain includes a WordDelimiterFilter and, later a filter that dow

Re: WordDelimiter

nd words concatenated, "100R8989 ". -- Jack Krupansky -Original Message- From: EXTERNAL Taminidi Ravi (ETI, Automotive-Service-Solutions) Sent: Friday, August 8, 2014 3:27 PM To: solr-user@lucene.apache.org Subject: WordDelimiter HI, I have a situation where I don't want to

Re: WordDelimiter

ns) wrote: > HI, I have a situation where I don't want to split the words, I am using > the workdelimterfilter where it works good. > > For eg. If I send to analyszer for 100-001 , it is not splitting the > keyword, but if I send 100-R8989 then the worddelimiter filter to 100

WordDelimiter

HI, I have a situation where I don't want to split the words, I am using the workdelimterfilter where it works good. For eg. If I send to analyszer for 100-001 , it is not splitting the keyword, but if I send 100-R8989 then the worddelimiter filter to 100 | R9889, below is the filed ana

Re: Fieldnorm solr 4 -> specialchars(worddelimiter)

e.com/Fieldnorm-solr-4-specialchars-worddelimiter-tp4036248p4036759.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Fieldnorm solr 4 -> specialchars(worddelimiter)

ieldnorm solr 4 -> specialchars(worddelimiter) Hello Jack, I'm using exactly the same fieldtype: It looks like the catenatewords has another influence in solr 4.1 than in pre

Re: Fieldnorm solr 4 -> specialchars(worddelimiter)

alyze is the same in both versions. I want exactly the same results but can't get it. -- View this message in context: http://lucene.472066.n3.nabble.com/Fieldnorm-solr-4-specialchars-worddelimiter-tp4036248p4036749.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Fieldnorm solr 4 -> specialchars(worddelimiter)

-Original Message- From: roySolr Sent: Monday, January 28, 2013 4:11 AM To: solr-user@lucene.apache.org Subject: Re: Fieldnorm solr 4 -> specialchars(worddelimiter) I have done some more testing with different examples. It's really the worddelimiter that influence the fieldnorm

Re: Fieldnorm solr 4 -> specialchars(worddelimiter)

I have done some more testing with different examples. It's really the worddelimiter that influence the fieldnorm. When i search for "Barcelona" the doc with "FC Barcelona" scores higher than "FC-Barcelona". Fieldnorm for "FC Barcelona" = 0.6

Fieldnorm solr 4 -> specialchars(worddelimiter)

Strange that in solr 3.1 it was just counting for 4 terms with the same filter. Why is fieldnorm different? I need some help with this:) Thanks Roy -- View this message in context: http://lucene.472066.n3.nabble.com/Fieldnorm-solr-4-specialchars-worddelimiter-tp4036248.html Sent from the

Re: WordDelimiter and stemEnglishPossessive doesn't work

THANK YOU!! I thought i only could use one character for the pattern.. Now i use a regular expression:) I don't need the wordDelimiter anymore. It's split on # and whitespace dataset: mcdonald's#burgerking#Free record shop#h&m mcdonald's burgerking free record shop

Re: WordDelimiter and stemEnglishPossessive doesn't work

un 14, 2011 at 6:15 AM, roySolr wrote: > Ok, with catenatewords the index term will be mcdonalds. But that's not what > i want. > > I only use the wordDelimiter to split on whitespace. I have already used the > PatternTokenizerFactory so i can't use the whitespacetokenizer.

Re: WordDelimiter and stemEnglishPossessive doesn't work

do you need the word delimiter ? #|\s i think its just regex in the pattern tokeniser - i might be wrong though ? On 14 June 2011 11:15, roySolr wrote: > Ok, with catenatewords the index term will be mcdonalds. But that's not what > i want. > > I only use the wordDeli

Re: WordDelimiter and stemEnglishPossessive doesn't work

Ok, with catenatewords the index term will be mcdonalds. But that's not what i want. I only use the wordDelimiter to split on whitespace. I have already used the PatternTokenizerFactory so i can't use the whitespacetokenizer. I want my index looks like this: dataset: mcdonald's#

Re: WordDelimiter and stemEnglishPossessive doesn't work

ds" in your index if stemEnglishPosessive=0 but not if you set stemEnglishPosessive=1. Hope that helps Erick On Fri, Jun 10, 2011 at 3:51 AM, roySolr wrote: > Hello, > > I have some problem with the wordDelimiter. My data looks like this: > > mcdonald's#burgerking#Free r

WordDelimiter and stemEnglishPossessive doesn't work

Hello, I have some problem with the wordDelimiter. My data looks like this: mcdonald's#burgerking#Free record shop#h&m I want to tokenize this on #. After that it has to split on whitespace. I use the wordDelimiter for that(can't use 2 tokenizers) Now this works but there is o

Looking for suggestion of WordDelimiter filter config and 'ALMA awards'

rch for 'alma awards' or 'ALMA awards', the right results came back as expected. I immediately went to solr/admin/analysis to see what is going on with indexing of 'ALMA awards' and query parsing of 'aLMA awards', and looks like WordDelimiter is the one caus