Re: Suggester case (in)sensitive

Does anyone have an idea? Thanks and best regards, Moe > Am 20.03.2019 um 15:19 schrieb Moritz Schmidt : > > Hello everyone. > > I’m trying to build autocomplete functionality. > My setup works but has one problem: > When using HighFrequencyDictionaryFactory the Suggestion-Results I get are >

Re: Suggester autocomplete for address information

I'd like to clarify that what I am looking for is the right field type for the address field that will suggest values as follows for the input: Input: "123 SM" Suggestions: - 123-127 SMITH STREET, KEMPSEY NSW 2440 - 123 SMYTHE STREET. RANDOM PLACE And in addition to this I want the se

Re: Suggester and fuzzy/infix suggestions

Another path to follow could be to design a specific collection(index) for the auto-suggestion. In there you can define the analysis chain as you like ( for example using edge-ngram filtering on top of tokenisation) to provide infix autocompletion. Then you can play with your queries as you like an

Re: Suggester and fuzzy/infix suggestions

Yes, but it is better than nothing. Don’t let the unavailable perfect solution keep you from implementing the available good solution. If you want to easily use fuzzy search with edismax, check out the patch submitted with SOLR-629. wunder Walter Underwood wun...@wunderwood.org http://observer.

Re: Suggester and fuzzy/infix suggestions

I thought about that - but that does not solve the issue. If the user types in a misspelled word, and that word is somewhere in the middle of the field, that result will not be returned. 2017-06-28 19:00 GMT+02:00 Walter Underwood : > I set up two suggesters, one fuzzy and one analyzing infix. Th

Re: Suggester and fuzzy/infix suggestions

I set up two suggesters, one fuzzy and one analyzing infix. That gives two sets of suggestions, so the client code has to merge them into one list and toss duplicates. They use the same weights, so I can keep the top weighted suggestions. wunder Walter Underwood wun...@wunderwood.org http://obs

Re: Suggester uses lots of 'Page cache' memory

Memory/cache aside, the fundamental Solr issue is that the Suggester build operation will read the entire index, even though very few docs have the relevant fields. Is there a way to set a 'fq' on the Suggester build? java.lang.Thread.State: RUNNABLE at org.apache.lucene.codecs.compres

Re: Suggester uses lots of 'Page cache' memory

Thanks Shawn, I'll have to look closer into this. On 3 May 2017 at 12:10, Shawn Heisey wrote: > On 5/2/2017 6:46 PM, Damien Kamerman wrote: > > Shalin, yes I think it's a case of the Suggester build hitting the index > > all at once. I'm thinking it's hitting all docs, even the ones without > >

Re: Suggester uses lots of 'Page cache' memory

On 5/2/2017 6:46 PM, Damien Kamerman wrote: > Shalin, yes I think it's a case of the Suggester build hitting the index > all at once. I'm thinking it's hitting all docs, even the ones without > fields relevant to the suggester. > > Shawn, I am using ZFS, though I think it's comparable to other setu

Re: Suggester uses lots of 'Page cache' memory

Shalin, yes I think it's a case of the Suggester build hitting the index all at once. I'm thinking it's hitting all docs, even the ones without fields relevant to the suggester. Shawn, I am using ZFS, though I think it's comparable to other setups. mmap() should still be faster, while the ZFS ARC

Re: Suggester uses lots of 'Page cache' memory

On 5/1/2017 10:52 PM, Damien Kamerman wrote: > I have a Solr v6.4.2 collection with 12 shards and 2 replicas. Each > replica uses about 14GB disk usage. I'm using Solaris 11 and I see the > 'Page cache' grow by about 7GB for each suggester replica I build. The > suggester index itself is very small

Re: Suggester uses lots of 'Page cache' memory

On Tue, May 2, 2017 at 10:22 AM, Damien Kamerman wrote: > Hi all, > > I have a Solr v6.4.2 collection with 12 shards and 2 replicas. Each replica > uses about 14GB disk usage. I'm using Solaris 11 and I see the 'Page cache' > grow by about 7GB for each suggester replica I build. The suggester inde

Re: Suggester Issue

Taking a look to the code, basically the context field act as the default field in a Standard Query Parser. Even if having multiple context fields seems to be supported when building the auxiliary suggester index, it doesn't seem to work at query time. If you specify the context only at query time

Re: Suggester Issue

Hi, Any update on this? Could you please let me know is it possible to pass CFQ parameter on multiple fields? Thanks On Tue, Jul 5, 2016 at 9:40 AM, Rajesh Kapur wrote: > Hi, > > > > I tried to implement suggester using SOLR 6.0.1 with context field. PFB > the configuration we are using to im

Re: Suggester Issue

Hi I have reinstalled the solr and it is working fine now. Couple of issues I am facing now are: 1. Cfq parameter is expecting only brand-name as configured. So now if I hv special character like - in brandname I am not able to fetch the suggestion 2 I want to fetch the suggestion filtered on 2

Re: Suggester Issue

>From a brief look to the config files it seems fine to me, but I didn't have the chance to try it. Have you checked that you have nothing in the Solr logs ? You can potentially need to debug. Cheers On Tue, Jul 5, 2016 at 10:10 AM, Rajesh Kapur wrote: > PFA the schema.xml and solrconfig.xml fo

Re: Suggester Issue

Hi, Thanks for the reply. Yes I am getting same result with and without suggest.cfq parameter. Thanks, Rajesh Kapur On Tue, Jul 5, 2016 at 2:08 PM, Alessandro Benedetti wrote: > Hi Rajesh, > I will take a look to your config as soon as I have 5 minutes, in the > meantime, can you specify what

Re: Suggester Issue

Hi Rajesh, I will take a look to your config as soon as I have 5 minutes, in the meantime, can you specify what is the output you get and what is the output you expect ? You simply don't get the filter applied ? Cheers On Tue, Jul 5, 2016 at 5:10 AM, Rajesh Kapur wrote: > Hi, > > > > I tried to

Re: Suggester needed for returning suggestions when term is not start of field value

You might consider different implementations. The FST-based suggesters only work in order by design. AnalyzingInfixSuggester or perhaps FreeTextSuggester are possibilities. Here's something you might find useful: http://lucidworks.com/blog/solr-suggester/ Best, Erick On Fri, Aug 7, 2015 at 5:1

Re: Suggester always highlights suggestions even if we pass highlight=false

Hi Nutch, are you sure you are using the proper parameters ? I can not see the "highlight" param in the suggester configuration! >From the issue you linked, it seems it is necessary to disable highlighting ( default =true) . I see it as query param for the /suggest search handler. Am I wrong or yo

Re: Suggester configuration queries.

Alessandro Benedetti, Thanks for the links. Regards, Sachin Vyas. -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-configuration-queries-tp4214950p4217234.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Suggester configuration queries.

Using the term component to get Auto-suggest is a very old approach, and gives minimal features… If it is ok for you, ok! I would suggest these reading for Auto suggestions : Suggester Solr wiki Solr suggester

Re: Suggester configuration queries.

Hi, For my reply dated "Jul 02, 2015; 4:47pm", for my scenario / test data, the results of Spellchecker of Solr 4.6 & 5.1 are fine. Also, the results of Suggester of Solr 4.6 & 5.1 are fine. I was mixing up the two components. Thanks & Regards, Sachin Vyas. -- View this message in context:

Re: Suggester configuration queries.

Hi, For my reply dated "Jul 02, 2015; 4:47pm", Actually *there is no difference in results* for "spellchecker" & "suggester" components in Solr 4.6 and Solr 5.1. I was actually mixing up the two components. Thanks & Regards, Sachin Vyas. -- View this message in context: http://lucene.472066.n

Re: Suggester configuration queries.

Hi, I am using the Solr Terms Component for auto-suggestion, this provides me the functionality as per my requirements. https://wiki.apache.org/solr/TermsComponent Regards, Sachin Vyas. -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-configuration-queries-tp4214

Re: Suggester configuration queries.

Any Suggestions on this ? Regards, Sachin Vyas. -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-configuration-queries-tp4214950p4216045.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Suggester duplicating values

Absolutely! Thanks man. []'s Rafael On Thu, Jul 2, 2015 at 12:42 PM, Alessandro Benedetti < benedetti.ale...@gmail.com> wrote: > That is what I was saying :) > Hope it helps > > 2015-07-02 16:32 GMT+01:00 Rafael : > > > Just double checking: > > > > In my ruby backend I ask for (using the given

Re: Suggester duplicating values

That is what I was saying :) Hope it helps 2015-07-02 16:32 GMT+01:00 Rafael : > Just double checking: > > In my ruby backend I ask for (using the given example) all suggested terms > that starts with "J." , then I (probably) add all the terms to a Set, and > then return the Set to the view. Righ

Re: Suggester duplicating values

Just double checking: In my ruby backend I ask for (using the given example) all suggested terms that starts with "J." , then I (probably) add all the terms to a Set, and then return the Set to the view. Right ? []'s Rafael On Thu, Jul 2, 2015 at 12:12 PM, Alessandro Benedetti < benedetti.ale...

Re: Suggester duplicating values

No, I was referring to the fact that a Suggester as a unit of information manages simple terms which are identified simply by themselves. What you need to do is tu sums some Ruby Datastructure that prevent the duplicates to be inserted, and then offer the Suggestions from there. Cheers 2015-07-0

Re: Suggester duplicating values

Thanks, Alessandro! Well, I'm using Ruby and the r-solr as a client library. I didn't get what you said about term id. Do I have to create this field ? Or is it a "hidden field" utilized by solr under the hood ? []'s Rafael On Thu, Jul 2, 2015 at 6:41 AM, Alessandro Benedetti < benedetti.ale...@

Re: Suggester configuration queries.

Erick, We actaully have a working version of Solr 4.6 Spellchecker, the configuration details are as mentioned below: *Solr 4.6 - schema.xml*

Re: Suggester duplicating values

Hi Rafael, Your problem is clear and it has actually been explored few times in the past. I agree with you in a first instance. A Suggester basic unit of information is a term. Not a document. This means that actually it does not make a lot of sense to return duplicates terms ( because they are co

Re: Suggester configuration queries.

that's where I'd start at least. Erick On Wed, Jul 1, 2015 at 6:56 AM, ssharma7...@gmail.com wrote: > Erick, > As per your reply - *"So for your situation, I'd use a copyField to a > minimally-analyzed field > and use the index-based suggesters."* > > Are you suggesting use of "spellCheck" c

Re: Suggester configuration queries.

Erick, As per your reply - *"So for your situation, I'd use a copyField to a minimally-analyzed field and use the index-based suggesters."* Are you suggesting use of "spellCheck" component in Solr, and in it "DirectSolrSpellChecker"? Regards, Sachin Vyas. -- View this message in context:

Re: Suggester configuration queries.

This will be pretty much unworkable for any large corpus. The DocumentDictionaryFactory builds its index by reading the stored value from every document in your index to put into a sidecar Solr index (for free text suggester). This can take many minutes so doing this on every commit is an anti-pat

Re: Suggester for text array

Hi Advait , First of all I suggest you to study Solr a little bit [1]. because your requirements are actually really simple : 1) You can simply use more than one suggest dictionary if you care to keep the suggestions separated ( keeping if a term is coming from the name or from the the category)

Re: suggester returning stems instead of whole words

yep, 4.3.1. The API changed after that so it’s finding the time to rewrite the entire backend that uses it On 17/06/2015 16:55, "Shalin Shekhar Mangar" wrote: >You must be using an old version of Solr. Since Solr 4.8 and beyond, >the and tags have been deprecated and you can place >the field a

Re: suggester returning stems instead of whole words

You must be using an old version of Solr. Since Solr 4.8 and beyond, the and tags have been deprecated and you can place the field and field type definitions anywhere in the schema.xml. See http://issues.apache.org/jira/browse/SOLR-5228 On Wed, Jun 17, 2015 at 9:09 PM, Alistair Young wrote: >

Re: suggester returning stems instead of whole words

working in a tiny tmux window does have some disadvantages, such as losing one’s place in the file! the subject_autocomplete definition wasn’t inside . Now that it is, everything is working. thanks for listening Alistair -- mov eax,1 mov ebx,0 int 80h On 17/06/2015 15:17, "Alistair Young" w

Re: suggester returning stems instead of whole words

looking at the schema browser, subject_autocomplete has a type of text_en rather than text_auto and all the terms are stemmed. Its contents are the same as the one it was copied from, dc.subject, which is text_en and stemmed. On 17/06/2015 14:58, "Erick Erickson" wrote: >Hmmm, shouldn't be happe

Re: suggester returning stems instead of whole words

Hmmm, shouldn't be happening that way. Spellcheck is supposed to be looking at indexed terms. If you go into the admin/schema browser page and look at the new field, what are the terms in the index? They shouldn't be stemmed. And I always get confused where this suggest is supposed to point. Do

Re: suggester returning stems instead of whole words

yep did both of those things. Getting the same results as using dc.subject On 17/06/2015 14:44, "Shalin Shekhar Mangar" wrote: >Did you change the SpellCheckComponent's configuration to use >subject_autocomplete instead of dc.subject? After you made that >change, did you invoke spellcheck.build=

Re: suggester returning stems instead of whole words

Did you change the SpellCheckComponent's configuration to use subject_autocomplete instead of dc.subject? After you made that change, did you invoke spellcheck.build=true to re-build the spellcheck index? On Wed, Jun 17, 2015 at 7:06 PM, Alistair Young wrote: > copyField doesn¹t seem to fix the s

Re: suggester returning stems instead of whole words

copyField doesn¹t seem to fix the suggestion stemming. Copying the field to another field of this type: but I¹m still getting stemmed suggestions after rebuilding the index. Alistair -- mov eax,1 mov ebx,0 int 80h On 17/06/2015 11:28, "Alistair Young" wrote: >ah look

Re: suggester returning stems instead of whole words

ah looks like I need to use copyField to get a non stemmed version of the suggester field Alistair -- mov eax,1 mov ebx,0 int 80h On 17/06/2015 11:15, "Alistair Young" wrote: >I was wondering if there's a way to get the suggester to return whole >words. Instead of returning 'technology' ,

Re: Suggester

This might help: http://lucidworks.com/blog/solr-suggester/ Best, Erick On Thu, May 14, 2015 at 12:43 PM, lreg wrote: > Could you please explain how you solved the problem I am having the same > issue :( > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Suggester-t

Re: Suggester

Could you please explain how you solved the problem I am having the same issue :( -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-tp4201287p4205460.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Suggester

OK, I found the problem and as so often it was sitting in front of the display. Now the next problem: The suggestions returned consist always of a complete text block where the match was found. I would have expected a single word or a small phrase. Thanks in advance Martin > Am 22.04.2015 um

Re: Suggester

Unfortunately, setting suggestAnalyzerFieldType to "text_suggest" didn’t change anything. The suggest dictionary is freshly built. As I mentioned before, only words or phrases of the source field „content“ are not matched. When querying the index, the response only contains „suggestions“ field da

Re: Suggester

Did you build your suggest dictionary after indexing? Kind of a shot in the dark but worth a try. Note that the suggest field of your suggester isn't using your "text_suggest" field type to make suggestions, it's using "text_general". IOW, the text may not be analyzed as you expect. Best, Erick

Re: Suggester Example In Documentation Not Working

: However, you will notice on page 228, under the section "Suggester", it : gives an example of a suggester search component using : solr.SpellCheckComponet. ... : So it would appear the solr.SuggestComponent has been around since 4.7, : but the documentation has not caught up with the

Re: Suggester Example In Documentation Not Working

rsday, January 22, 2015 12:50:46 PM Subject: Re: Suggester Example In Documentation Not Working 1) which version of Solr are you using? (note that the online HTML ref guide is a DRARFT that applies to 5.0 - you may want to review the specific released version of the ref guide that app

Re: Suggester Example In Documentation Not Working

1) which version of Solr are you using? (note that the online HTML ref guide is a DRARFT that applies to 5.0 - you may want to review the specific released version of the ref guide that applies to your version of solr: http://archive.apache.org/dist/lucene/solr/ref-guide/ 2) the behavior of th

Re: Suggester Example In Documentation Not Working

I see that the docs say that the doc needs to be indexed only, but for Fuzzy or Analyzed, I think the field needs to be stored. On the other side, not sure how much sense it makes to use any of those two implementations if the field type you want to have is "string". Tomás On Thu, Jan 22, 2015 at

Re: Suggester: weight (term frequency) and 'mm' feasibility (allTermsRequired)

Hi, Re. AND/OR boolean lookup for ‘infix’ suggestion. I checked that Lucene does have an underlying support for this via the “allTermsRequired” boolean. However this feature, along with highlighting (on/off) are currently hardwired in Lucene, and hidden in Solr. This issue has previously been

Re: Suggester not suggesting anything using DictionaryCompoundWordTokenFilterFactory

I think I found the problem. The definition of the suggester component has a "field" option which references the field that the suggester uses to generate suggestions. Changing this to the field using the DictionaryCompundWordTokenFilterFactory also suggests word parts. Am 11.11.2014 08:52 schrie

Re: Suggester on Dynamic fields

Hi Ramzi, First thanks for your comments. Regarding your line parameters.set("qt", /suggest") My understanding is that "suggest" has to be a handler defined in SolrConfig.xml. And the handler needs to have one of more defined (search) component(s). The search component syntax needs diction

Re: Suggester on Dynamic fields

Use query() to have Solr search for results. You have to pass a SolrQuery object that describes the query, and you will get back a QueryResponse (from the org.apache.solr.client.solrj.response package). SolrQuery has methods that make it easy to add parameters to choose a request handler and send p

Re: Suggester - how to return exact match?

Thanks! We solved this issue in the front-end now. I.e. we add the exact match to the list of suggestions there. Mirko 2013/11/22 Developer > Might not be a perfect solution but you can use edgengram filter and copy > all > your field data to that field and use it for suggestion. > > position

Re: Suggester - how to return exact match?

Might not be a perfect solution but you can use edgengram filter and copy all your field data to that field and use it for suggestion. http://localhost:8983/solr/core1/select?q=name:iphone The above query will return iphone iphone5c iphone4g -- View thi

Re: Suggester - how to return exact match?

Hi, I'd like to clarify our use case a bit more. We want to return the exact search query as a suggestion only if it is present in the index. So in my example we would expect to get the suggestion "foo" for the query "foo" but no suggestion "abc" for the query "abc" (because "abc" is not in the di

Re: Suggester - how to return exact match?

May be there is a way to do this but it doesn't make sense to return the same search query as a suggestion (Search query is not a suggestion as it might or might not be present in the index). AFAIK you can use various look up algorithm to get the suggestion list and they lookup the terms based on

Re: Suggester - multivalued field

I just tried it with Solr 4.0 and it worked fine, for me. I used the "cat" field of the Solr example, which is a multivalued "string" field. My data: curl http://localhost:8983/solr/update?commit=true -H 'Content-type:application/csv' -d ' id,cat,cat,cat d-1,aardvark,abacus,accord d-2,aboar

Re: Suggester with punctuation signs

Hi! Upayavira: Hi I'm using the standard tokenizer right now, and it's working fine, but I was wondering if there is any form I can strip this punctuation marks right in the suggest requestHandler, so no need for index again. I've been doing some tests and increasing the threshold has improved

Re: Suggester with punctuation signs

You may want to change your tokenisation anyhow, as a search for 'universidad' will not match your term 'universidad,' But you are on the right track - to improve suggestions, improve what is in your index. Upayavira On Mon, Nov 26, 2012, at 07:54 PM, Jorge Luis Betancourt Gonzalez wrote: > Hi:

Re: Suggester for numbers

Hi, Does StandardTokenizerFactory remove your numbers? Go to the Analysis page in Solr Admin, enter your query with numbers, and see what happens. Otis -- SOLR Performance Monitoring - http://sematext.com/spm/index.html Search Analytics - http://sematext.com/search-analytics/index.html On Thu

Re: Suggester for numbers

Hello Illu, Here you go: -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-fo

Re: suggester issues

Hi, I m also facing same issue while using suggester (working in c#.net). Below is my configurations. suggest/?q="michael ja" --- Response : - - 0 1 - - -

Re: Suggester component replication

Hmmm, you haven't said which version of Solr you use, but according to: https://issues.apache.org/jira/browse/SOLR-866 it's not supported. But I think the new 4.0 stuff doesn't use the "sidecar" index to store this stuff, it just walks the internal data structures for that field so it may never be

Re: suggester/autocomplete locks file preventing replication

pocking into the code i think the FileDictionary class is the culprit: It takes an InputStream as a ctor argument but never releases the stream. what puzzles me is that the class seems to allow a one-time iteration and then the stream is useless, unless i'm missing smth. here. is there a good

Re: suggester/autocomplete locks file preventing replication

BTW: a core unload doesnt release the lock either ;( On 21.06.2012 14:39, tom wrote: hi, i'm using the suggester with a file like so: suggest name="classname">org.apache.solr.spelling.suggest.Suggester name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup

Re: Suggester not working for digit starting terms

On Thu, Apr 12, 2012 at 3:52 PM, jmlucjav wrote: > Well now I am really lost... > > 1. yes I want to suggest whole sentences too, I want the tokenizer to be > taken into account, and apparently it is working for me in 3.5.0?? I get > suggestions that are like "foo bar abc".  Maybe what you mention

Re: Suggester not working for digit starting terms

Well now I am really lost... 1. yes I want to suggest whole sentences too, I want the tokenizer to be taken into account, and apparently it is working for me in 3.5.0?? I get suggestions that are like "foo bar abc". Maybe what you mention is only for file based dictionaries? I am using the field

Re: Suggester not working for digit starting terms

On Wed, Apr 11, 2012 at 4:37 PM, jmlucjav wrote: > Just to be sure, reproduced this with example config from 3.5. > Regardless of your tokenizer, be aware that with this version of solr its going to split up terms based on 'identifier rules' (including splitting on whitespace). This is because su

Re: Suggester not working for digit starting terms

Just to be sure, reproduced this with example config from 3.5. 1. add to schema.xml

Re: Suggester not working for digit starting terms

Hmmm, I can't pursue this right now, anyone want to jump in? Erick On Tue, Apr 10, 2012 at 2:41 PM, jmlucjav wrote: > I have double checked and still get the same behaviour. My field is: >                 positionIncrementGap="100"> >                         >                                 cla

Re: Suggester not working for digit starting terms

I have double checked and still get the same behaviour. My field is: Analisys

Re: Suggester not working for digit starting terms

Is it possible that your fieldType definition for a_suggest is stripping out the digits? Consider using TermsComponent http://wiki.apache.org/solr/TermsComponent or the admin page or Luke to examine the terms actually _in_ your index. Or look at the admin/analysis page and give it some sample input

Re: Suggester for Numbers

: http://lucene.472066.n3.nabble.com/Re-Suggester-for-Numbers-tp3698125p3698154.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Suggester for Numbers

Hello people! Did you manage to make suggester return suggestions for numbers? I have the same problem and could not make it with schema changes that Erick described. Thanks a lot.

Re: Suggester for Numbers

Well, by setting generateNumberParts="0" you've excluded numbers from the index, so they aren't there for auto-suggest. Try setting it to "1" and reindexing Best Erick On Dec 9, 2011 4:57 PM, "Awasthi, Shishir" wrote: > Is there a way to make suggester return suggestion for numbers also? > >

Re: suggester issues

s for your help. -- From: "William Oberman" Sent: Friday, August 19, 2011 5:07 PM To: Subject: Re: suggester issues Hard to say, so I'll list the exact steps I took: -Downloaded apache-solr-3.3.0 (I like to stick with releases vs. svn) -Untar and cd -ant -Wrote my class be

Re: suggester issues

2011 5:07 PM To: Subject: Re: suggester issues Hard to say, so I'll list the exact steps I took: -Downloaded apache-solr-3.3.0 (I like to stick with releases vs. svn) -Untar and cd -ant -Wrote my class below (under a peer directory in apache-solr-3.3.0) -javac -cp ../dist/apache-solr-core-3.3.0

Re: suggester issues

> org.apache.solr.spelling.QueryConverter". > > What am I doing wrong? > > -- > From: "William Oberman" > Sent: Thursday, August 18, 2011 10:35 PM > To: > Subject: Re: suggester issues > >> I t

Re: suggester issues

nverter". What am I doing wrong? -- From: "William Oberman" Sent: Thursday, August 18, 2011 10:35 PM To: Subject: Re: suggester issues I tried this: package com.civicscience; import java.util.ArrayList; import java.util.C

Re: suggester issues

I tried this: package com.civicscience; import java.util.ArrayList; import java.util.Collection; import java.util.Collections; import org.apache.lucene.analysis.Token; import org.apache.solr.spelling.QueryConverter; /**

Re: suggester issues

It can be done, I did that with shingles, but it's not the way it's meant to be. The main problem with suggester is that we want compound words and we never get them. I try to get "internet explorer" but when i enter in the second word, "internet e" the suggester never finds "explorer". 2011/8/18

Re: suggester issues

I was trying to deal with the exact same issue, with the exact same results. Is there really no way to feed a phrase into the suggester (spellchecker) without it splitting the input phrase into words? -- View this message in context: http://lucene.472066.n3.nabble.com/suggester-issues-tp3262718p

Re: suggester issues

The problem lies in the suggester like the spellchecker, tokenizing on whitespace. So while shingles might give you nice suggestions, the behaviour of the Suggester makes it unusable. Besides that, I never succeeded in getting the suggester to show more collations then one. Normal spellchecker on

Re: suggester issues

What happens if you set spellcheck.maxCollations to more than 1? -- From: "Alexei Martchenko" Sent: Wednesday, August 17, 2011 11:01 PM To: Subject: Re: suggester issues I've been indexing and reindexing stuff here with Sh

Re: suggester issues

I've been indexing and reindexing stuff here with Shingles. I don't believe it's the best approach. Results are interesting, but I believe it's not what the suggester is meant to be. I tried but I got compound words in the suggestion itself. If you query them like http://localhost:

Re: suggester issues

I have the very very very same problem. I could copy+paste your message as mine. I've discovered so far that bigger dictionaries work better for me, controlling threshold is much better than avoid indexing one or twio fields. Of course i'm still polishing this. At this very moment I was looking in

Re: suggester component from trunk throwing error

i had a old jar in build. Everything works fine now -- View this message in context: http://lucene.472066.n3.nabble.com/suggester-component-from-trunk-throwing-error-tp3184736p3185681.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Suggester or spellcheck return stored fields

Hmmm, I don't quite get how this would work. There is really no association between terms from one field and terms from another. As I read your message, you have a PM from user1 with a term in some field of interest, call it "suggestion". A PM from user2 also has the term "suggestion". Now you want

Re: Suggester with multi terms

blocky, Shingles should be your way. Regards, Em -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-with-multi-terms-tp2859547p2860419.html Sent from the Solr - User mailing list archive at Nabble.com.