Suggester using up memory

suggester_fuzzy_dir HighFrequencyDictionaryFactory TextField TextField false false Is there a problem in our configuration?How can we make sure the build up of the suggester does not run out of memory? How do we determine the actual memory requirements in t

Solr Server Context Filtering in Auto Suggester not working

SOLR-14780?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel And below you'll find again the same information in case it's deleted or you do not have access to it anymore. I'm experiencing problem when I try to use Context Filtering with auto suggester. What I want is to filter the s

Suggester not suggesting but spellchecker is

Hello, Any advice on the following suggester not suggesting issue would be very welcome. I can get suggestions when using a spell checker but not when using the suggester. Both types are querying the same suggestion field. I'm using the following set

deduplicated suggester

Hi, I wrote suggester based on AnalyzingInfixSuggester that deduplicates data on defined key pattern. Source code is on github: https://github.com/hlavki/solr-unique-suggester[1] m. [1] https://github.com/hlavki/solr-unique-suggester

allTermsRequired not working for me with suggester

Hi folks, I have allTermsRequired=true defined in the suggester component. Despite of this if I run the following query: http://localhost:8983/solr/pocwithedgengram/suggesthandler?allTermsRequired=true&q=*%3A*&suggest.q=Arany%20J%C3%A1nos I get back the following result (it is only a sni

Re: deduplication of suggester results are not enough

Hi Roland, I wrote AnalyzingInfixSuggester that deduplicates data on several levels at index time. I will publish it in few days on github. I'll wrote to this thread when done. m. On štvrtok 26. marca 2020 16:01:57 CET Szűcs Roland wrote: > Hi All, > > I follow the discussion of

deduplication of suggester results are not enough

Hi All, I follow the discussion of the suggester related discussions quite a while ago. Everybody agrees that it is not the expected behaviour from a Suggester where the terms are the entities and not the documents to return the same string representation several times. One suggestion was to

Re: configuring suggester with api

according to docs at lucene.apache.org/solr/guide/8_4/suggester.html# <https://lucene.apache.org/solr/guide/8_4/suggester.html#> that parameter is optional ( i am supplying it as url param). I guess i have a problem with JSON payload to create suggester, but in that case api should err

Re: configuring suggester with api

ary field, and our suggester (which is working) also has this field: http://localhost:8983/solr/techproducts/suggest?suggest=true&suggest.build=true&suggest.dictionary=mySuggester&suggest.q=c&suggest.cfq=memory On 3/12/20, 6:33 AM, "Manoj Sonawane" wrote: Hello,

configuring suggester with api

Hello, I am trying to learn solr config api and having problem creating suggester. Any pointers will be appriciated suggester has been setup with curl -X POST -H 'Content-type:application/json' --data-binary '{ "add-searchcomponent": { "class"

configuring suggester with api

Hello, I am trying to learn solr config api and having problem creating suggester. Any pointers will be appriciated suggester has been setup with curl -X POST -H 'Content-type:application/json' --data-binary '{ "add-searchcomponent": { "class"

Re: Solr suggester : duplicate suggestions

gt; > Although I handle Auto-Suggest, I have worked a little with Suggester > component. Suggester provides results as you type. Do you really need it? > > Also, I don't know if I'm correct, but where have you described '&' to be > replaced with 'and'?

Re: Solr suggester : duplicate suggestions

Hi Dhanesh, Although I handle Auto-Suggest, I have worked a little with Suggester component. Suggester provides results as you type. Do you really need it? Also, I don't know if I'm correct, but where have you described '&' to be replaced with 'and'? Is '

Solr suggester : duplicate suggestions

Dear all, I'm facing two issues with solr suggester component. *First * If I typed "Fire and safety", I'll get the result. But If I type "Fire & safety" suggester is not showing *Second* I'm getting duplicate suggestions in suggester

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

This setting is pretty dangerous. It’ll build the suggester every time the Solr instance starts. The DocumentDictionaryFactory will read _every_ document in your index to extract the stored “suggest” field and create the dictionary. But this points to the fact that you hadn’t built the

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

2019 at 3:11 PM Tyrone Tse wrote: > What's the command to build it > > > On Wed, Nov 6, 2019 at 3:06 PM Mikhail Khludnev wrote: > >> Hello, >> >> Have you build suggester before requesting? >> >> On Wed, Nov 6, 2019 at 12:50 PM Tyrone Tse

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

What's the command to build it On Wed, Nov 6, 2019 at 3:06 PM Mikhail Khludnev wrote: > Hello, > > Have you build suggester before requesting? > > On Wed, Nov 6, 2019 at 12:50 PM Tyrone Tse wrote: > > > Solr version 8.1.1 > > > > My schema >

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

Hello, Have you build suggester before requesting? On Wed, Nov 6, 2019 at 12:50 PM Tyrone Tse wrote: > Solr version 8.1.1 > > My schema > > multiValued="false" indexed="true"/> > > > solconfig.xml > > > >

Error with Solr Suggester using lookupIml = FreeTextLookupFactory

Solr version 8.1.1 My schema solconfig.xml mySuggester FreeTextLookupFactory DocumentDictionaryFactory suggest 3 text_en_splitting false tru

Behavior of a Solr suggester using spellchecker

Dear Solr community, I am facing a behavior with a suggest request handler that does not look normal to me, and I would like to understand. * Here is the configuration of the suggest component : suggest org.apa

Problem with Solr alias and suggester call

ses.json content: { "responseHeader":{ "status":0, "QTime":0}, "aliases":{ "AT":"AT.test", "BE":"BE.test", "DE":"DE.test", "FR":"FR.test", "L

Re: Problem with solr suggester in case of non-ASCII characters

Hi Erick, Thanks your advice. I already removed it from the field definition used by the suggester and it works great. I will consider to took it from the entire processing of the other fields. I have only 7000 docs with index size of 18MB so far, so the memory footprint is not a key issue for

Re: Problem with solr suggester in case of non-ASCII characters

lysis-screen.html) and tell >> how >> the term is analyzed for both query and index? >> >> Kind Regards, >> Furkan KAMACI >> >> On Tue, Jul 30, 2019 at 4:50 PM Szűcs Roland >> wrote: >> >>> Hi All, >>> >&g

Re: Problem with solr suggester in case of non-ASCII characters

zed for both query and index? > > Kind Regards, > Furkan KAMACI > > On Tue, Jul 30, 2019 at 4:50 PM Szűcs Roland > wrote: > > > Hi All, > > > > I have an author suggester (searchcomponent and the related request > > handler) defined in solrconfig: >

Re: Problem with solr suggester in case of non-ASCII characters

Hi Roland, Could you check Analysis tab ( https://lucene.apache.org/solr/guide/8_1/analysis-screen.html) and tell how the term is analyzed for both query and index? Kind Regards, Furkan KAMACI On Tue, Jul 30, 2019 at 4:50 PM Szűcs Roland wrote: > Hi All, > > I have an author

Problem with solr suggester in case of non-ASCII characters

Hi All, I have an author suggester (searchcomponent and the related request handler) defined in solrconfig: > author AnalyzingInfixLookupFactory DocumentDictionaryFactory BOOK_productAuthor short_text_hu suggester_infix_author false fa

Re: Problems using a suggester component in the /select handler in cloud mode

true > > > > suggest_infix_shingle > AnalyzingInfixLookupFactory > suggestInfixShingleDir > name="suggestAnalyzerFieldType">text_suggest_phrase > suggest

Re: Problems using a suggester component in the /select handler in cloud mode

    suggest_infix_shingle     AnalyzingInfixLookupFactory     suggestInfixShingleDir     name="suggestAnalyzerFieldType">text_suggest_phrase     suggest_phrase     true     true     true    

Suggester not returning all possible completions for a query in a large index

Hello Everyone, I'm using suggesters with Solr 6.4 to get suggestions for a field with a decent number of different values across a large number of documents that is configured like this: vendorSuggester BlendedInfixLookupFactory 600 false DocumentDictionaryFactory attrib

Problems using a suggester component in the /select handler in cloud mode

    suggest_infix_shingle     AnalyzingInfixLookupFactory     suggestInfixShingleDir     name="suggestAnalyzerFieldType">text_suggest_phrase     suggest_phrase     true     t

Re: SOLR Suggester returns either the full field value or single terms only

On Wed, Jun 19, 2019 at 12:20:43PM -0700, ppunet wrote: > As the SuggeterComponent provides the 'entire content' of the field in the > suggestions. How is it possible to have Suggester to return only part of the > content of the field, instead of the entire content, which in

Re: How to have Suggester to return part of the content instead of the entire content in Solr version 7.6.0?

What would you recommend to use for the search field autocomplete functionality? Considering I have the whole pdf content, and the user can start searching for any term from the pdf. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: SOLR Suggester returns either the full field value or single terms only

Hey, As the SuggeterComponent provides the 'entire content' of the field in the suggestions. How is it possible to have Suggester to return only part of the content of the field, instead of the entire content, which in my scenario quite long? -- Sent from: http://lucene.472066.n3.

Re: How to have Suggester to return part of the content instead of the entire content in Solr version 7.6.0?

you're mis-using suggester. It’s purpose is to return the entire contents of the “document”, to handle, specifically, multi-word suggestions, typically just a few words, often 2-4. Putting a large text field instead is outside the design. Also remember that the suggester is looking fo

How to have Suggester to return part of the content instead of the entire content in Solr version 7.6.0?

content' of the field in the suggestions. How is it possible to have Suggester to return only part of the content of the field, instead of the entire content, which in my scenario quite long? Thanks in advance. PD -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Solr's suggester results

of the field in the suggestions. How is it possible to have Suggester to return only part of the content of the field, instead of the entire content, which in my scenario quite long? Thanks in advance. PD -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

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: Why can't we get multiple payloadFields from suggester?

Did you find out a way to get multiple payloadFields ? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Suggester case (in)sensitive

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 all lowercase as defined in my schema.xml: Without the LowerCaseFilterFactory I get my results as I wa

Re: Solr Suggester component not returning any results

Hi, Will you be able to post your configurations for your /suggest requestHandler in solrconfig.xml? Regards, Edwin On Wed, 20 Mar 2019 at 02:40, Deoxyribonucleic_DNA ... < deoxyribonucleic_...@hotmail.com> wrote: > Hi, I'm trying to implement the suggester component in Solr, b

Solr Suggester component not returning any results

Hi, I'm trying to implement the suggester component in Solr, based off the tutorial: https://lucene.apache.org/solr/guide/7_7/suggester.html#suggester-search-component-parameters I'm not getting any errors about how the suggester is set up or anything, but when I try to use it I get

Re: Suggester autocomplete for address information

"float" multiValued="false" indexed="true" stored="true"/> "locality_location" type="location" multiValued="false" indexed="true" > stored="true"/> "false" indexed="true" st

Suggester autocomplete for address information

Hi All, I'm new to Solr & the community so feel free to ignore / remove if this is the incorrect mailing list for this query. I'm trying to build an autocomplete using a Solr index for addresses in a format similar to: 123 Smith Street, KEMPSEY, NSW 2440 I'm looking to have these addresses sugg

Re: Scores with Solr Suggester

Hi Christine, it depends on the suggester implementation, the one that got closer in having a score implementation is the BlendedInfix[1] but it is still in the TO DO phase. Feel free to contribute it if you like ! [1] https://sease.io/2018/06/apache-lucene-blendedinfixsuggester-how-it-works-bugs

Re: Scores with Solr Suggester

field. If suggestions should be returned in a re-ordered way already, it would have to be done in such a search component as well. Cheers, Chris On Mon, Jul 2, 2018 at 8:31 PM, Buckler, Christine < christine.buck...@nordstrom.com> wrote: > Is it possible to return a score field for

Scores with Solr Suggester

Is it possible to return a score field for Suggester results like it does with standard search? I am looking for the score which quantifies how close of a match between type entered and suggestion result (not the weight associated with the suggestion). Is this possible? Christine Buckler

Re: analyzing infix suggester building in near real time LUCENE-5477

There was nothing like that year ago. Patches are welcome. On Mon, May 21, 2018 at 6:35 PM, Matteo Grolla wrote: > Hi everyone, > I'm evaluating suggesters that can can be in near real time and I came > across > https://issues.apache.org/jira/browse/LUCENE-5477. > Is there a way to use this

analyzing infix suggester building in near real time LUCENE-5477

Hi everyone, I'm evaluating suggesters that can can be in near real time and I came across https://issues.apache.org/jira/browse/LUCENE-5477. Is there a way to use this functionality from solr? Thanks very much Matteo Grolla

Re: How to implement Solr auto suggester and spell checker simultaneously on a single search box

Hi Sonal, if you want to go with a plain Solr suggester, what about the : FuzzyLookupFactory ? 1) it does support fuzzy matching ( spellcheck) 2) it does support auto complete If you want the context filtering as well, unfortunately the FST based Solr suggesters don't support this featur

How to implement Solr auto suggester and spell checker simultaneously on a single search box

Hello, I am using Solr version 6.3 and I want to implement a search box with auto suggester, spell checker and context filtering functionalities. I have explored around search components '*suggest*' and '*spellcheck*', but I found nothing which has all the 3 requirements ful

Re: solr 5.2->7.2, suggester failure

gt; > and was wondering if anyone had a quick idea right off the top of > their > > > > head. > > > > > > > > solrconfig: > > > > > > > > > > > > > > > > fixspell > > > > FuzzyLookupF

Re: solr 5.2->7.2, suggester failure

gt; solrconfig: > > > > > > > > > > > > fixspell > > > FuzzyLookupFactory > > > > > > string > > > > > > DocumentDictionaryFactory > > >

Re: solr 5.2->7.2, suggester failure

ondering if anyone had a quick idea right off the top of their > > head. > > > > solrconfig: > > > > > > > > fixspell > > FuzzyLookupFactory > > > > string > > > > DocumentDictionaryFactory > > tit

Re: solr 5.2->7.2, suggester failure

gt; > > > fixspell > FuzzyLookupFactory > > string > > DocumentDictionaryFactory > title > true > true > > > > received error: > > > ERROR true > SuggestComponent > Exception in building suggester index for:

solr 5.2->7.2, suggester failure

DocumentDictionaryFactory title true true received error: ERROR true SuggestComponent Exception in building suggester index for: fixspell java.lang.IllegalArgumentException: input automaton is too large: 1001 at org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse

Re: Multiple context fields in suggester component

You can start from here : org/apache/solr/spelling/suggest/SolrSuggester.java:265 Cheers - --- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Multiple context fields in suggester component

Thanks Alessandro Benedetti for the response. Can you please share the resources, so that I can explore more about customization of context filter. On Tue, Feb 13, 2018 at 5:01 PM, Alessandro Benedetti wrote: > Simple answer is No. > Only one context field is supported out of the box. > The quer

Re: Multiple context fields in suggester component

Simple answer is No. Only one context field is supported out of the box. The query you provide as context filtering query ( suggest.cfq= ) is going to be parsed and a boolean query for the context field is created [1]. You will need some customizations if you are targeting that behavior. [1] quer

Multiple context fields in suggester component

Hello All, Is there any way to set multiple context fields in suggester component? Or is there any way to apply multiple filters with suggester component in solr? Thanks Renuka Srishti

AW: Build suggester in different directory (not /tmp).

icht- Von: Erick Erickson [mailto:erickerick...@gmail.com] Gesendet: Mittwoch, 20. Dezember 2017 19:09 An: solr-user Betreff: Re: Build suggester in different directory (not /tmp). bq: this means I will need to set buildOnCommit and buildOnStartup to false. Be _very_ careful with these setti

Re: Build suggester in different directory (not /tmp).

> On Wed, Dec 20, 2017 at 2:58 PM, Shawn Heisey > wrote: > > > >> On 12/20/2017 10:05 AM, Matthew Roth wrote: > >> > I am building a few suggester's and I am receiving the error that I > have > >> no > >> > space left on device. > &g

Re: Build suggester in different directory (not /tmp).

m receiving the error that I have >> no >> > space left on device. >> >> >> >> > At first this threw me. df showed I had over 100 G free. the /data dir >> the >> > suggester is being constructed from is only 4G. On a subsequent run I &g

Re: Build suggester in different directory (not /tmp).

t; > space left on device. > > > > > At first this threw me. df showed I had over 100 G free. the /data dir > the > > suggester is being constructed from is only 4G. On a subsequent run I > > notice that the suggester is first being built in /tmp. When setting up > the &

Re: No space left on device - When I execute suggester component.

It's kind of scary how often serendipity plays it's part. See the thread titled: "Build suggester in different directory (not /tmp)." Which basically says that the suggester is being built in /tmp which may be limited. And yes, that's where it gets built by defau

Re: Build suggester in different directory (not /tmp).

On 12/20/2017 10:05 AM, Matthew Roth wrote: > I am building a few suggester's and I am receiving the error that I have no > space left on device. > At first this threw me. df showed I had over 100 G free. the /data dir the > suggester is being constructed from is only 4G. On a

Re: No space left on device - When I execute suggester component.

Hi Shawn/Erick/Matt, I agree with you. When I execute the command df -h I am getting the complete list of nfs mount info and Size and available space. I just shared one liner out of it.. One more thing I observed whenever I run suggest.build. *http://rn.com:8989/solr/LW_Data/

Re: Build suggester in different directory (not /tmp).

bq: this means I will need to set buildOnCommit and buildOnStartup to false. Be _very_ careful with these settings. Building your suggester can read the stored field(s) from _every_ document in your index to build which can take a very long time (perhaps hours). You'd pay that penalty every

Re: Build suggester in different directory (not /tmp).

t; java.io.IOException: No space left on device at > sun.nio.ch.FileDispatcherImpl.write0(Native Method) at > ... > > > > At first this threw me. df showed I had over 100 G free. the /data dir > the suggester is being constructed from is only 4G. On a subsequent run I > noti

Re: No space left on device - When I execute suggester component.

Oh, this seems relevant to my recent post to the list. My problem is that the suggester's are first being built in /tmp and moved to /var. tmp has a total of 2g's free whereas /var has near 100G. Perhaps you are running into the same problem I am in this regard? How does your /tmp dir look when bu

Build suggester in different directory (not /tmp).

100 G free. the /data dir the suggester is being constructed from is only 4G. On a subsequent run I notice that the suggester is first being built in /tmp. When setting up the LVM I only allotted 2g's to that directory and I prefer to keep it that way. Is there a way to build the suggest

Re: No space left on device - When I execute suggester component.

On 12/20/2017 12:21 AM, Fiz Newyorker wrote: I tried df -h , during suggest.build command. Size. Used Avail Use% Mounted on 63G 17G 44G 28% /ngs/app That cannot be the entire output of that command. Here's what I get when I do it: root@smeagol:~# df -h Filesystem Size

Re: No space left on device - When I execute suggester component.

Thank You Erick & Shawn for your response. I tried df -h , during suggest.build command. Size. Used Avail Use% Mounted on 63G 17G 44G 28% /ngs/app /ngs/app/razord/LWSearch/solr-6.5.0/bin - My Solr Server . I believe 44G is enough for running suggest.build. Please let me know wh

Re: No space left on device - When I execute suggester component.

On 12/19/2017 7:07 PM, Fiz Newyorker wrote: Yes I checked the Disk usage. using this command du -sh and I have enough space on the Disk. 2017-12-20 02:05:53.910 ERROR (qtp401424608-16) [ x:User_Data] o.a.s.s.HttpSolrCall null:java.io.IOException: No space left on device The error that

Re: No space left on device - When I execute suggester component.

How much is "enough"? You're going to be building and storing the resultant structure on disk since you have suggest.build=true. It seems simple enough to give yourself some more disk space and try again. While you do that, monitor the disk space while the suggester builds and se

Re: No space left on device - When I execute suggester component.

Hi , Yes I checked the Disk usage. using this command du -sh and I have enough space on the Disk. I am using this Query : *http://rn.com/solr/User_Data/suggest?suggest=true&suggest.build=true&suggest.dictionary=fuzzySuggester&wt=json&suggest.q=Jerry

Re: No space left on device - When I execute suggester component.

Have you checked disk consumption on the box yet? On Dec 19, 2017 8:46 PM, "Fiz Newyorker" wrote: > Hello Solr Experts, > > Good Evening ! > > I have an issue , Whenever I run the Auto Suggest component , > > http://lapp81.rno.com:8989/solr/Data/suggest?suggest= > true&suggest.build=true&sugges

No space left on device - When I execute suggester component.

Hello Solr Experts, Good Evening ! I have an issue , Whenever I run the Auto Suggest component , http://lapp81.rno.com:8989/solr/Data/suggest?suggest=true&suggest.build=true&suggest.dictionary=fuzzySuggester&wt=json&suggest.q=Jerry I am getting the following Error . {"responseHeader":{"statu

Clarification on Suggester Component of Solr 6.5.1

Hi All, Last day I was able to configure Solr Suggester for recommendation in my site with the following settings mySuggester AnalyzingLookupFactory DocumentDictionaryFactory query_suggest

Solr suggester build takes a very long time

So when following command is run to build solr suggester: ?suggest.build=true It takes a very long time to finish. I found out that this is because each time dictionary is built, it does not build delta, it rebuilds the entire dictionary. Is there a way to speed up the suggester build time? TIA

RE: Search suggester - threshold parameter

2017 15:41 To: solr-user@lucene.apache.org Subject: Search suggester - threshold parameter Does any of the phrase suggesters in Solr 6.1 honor the threshold parameter? I made following changes to enable phrase suggestion in my environment. Played with different threshold values but looks lik

Search suggester - threshold parameter

Does any of the phrase suggesters in Solr 6.1 honor the threshold parameter? I made following changes to enable phrase suggestion in my environment. Played with different threshold values but looks like the parameter is not being used. mySuggester FuzzyLookupFactory suggester_fu

Search suggester - threshold parameter

Does the threshold parameter work with any of the phrase suggestion component? https://lucene.apache.org/solr/guide/6_6/suggester.html AnalyzingInfixSuggester BlendedInfixLookupFactory DocumentDictionaryFactory title price text_en *0.005* The wiki page does not mention

RE: Phrase suggester - field limit and order

thanks for your reply. I'm not seeing any documentation explaining exactly how the weightField is used. So, is it just a field which I define on each document and populate with some number during index. And during search it will be used to sort the suggestions? -- Sent from: http://lucene.47206

Using the suggester component on distributed indexes

Hi all, I know the suggester component will work on distributed indexes. It works fine when I'm only using the suggester component in the components chain, but I'd like to apply the suggester to the end of the default components chain (query, facet, mlt, etc..). When I do, I get an

RE: Phrase suggester - field limit and order

heers, Peter. -Original Message- From: ruby [mailto:rshoss...@gmail.com] Sent: 09 November 2017 19:29 To: solr-user@lucene.apache.org Subject: Phrase suggester - field limit and order I'm using the BlendedInfixLookupFactory to get phrase suggestions. It returns the entire field content.

Phrase suggester - field limit and order

I'm using the BlendedInfixLookupFactory to get phrase suggestions. It returns the entire field content. I've tried the others and they do the same. AnalyzingInfixSuggester BlendedInfixLookupFactory DocumentDictionaryFactory title price text_en Is there a way to only return a fracti

Re: Quick quester about suggester component

Yep. Understood. On Tue, Oct 17, 2017, 8:14 PM Erick Erickson wrote: > Well, you tell the suggester what field to use in the first place in > the configuration. > > But I don't quite understand. Suggester is not _intended_ to return > documents. It returns, well, suggestion

Re: Quick quester about suggester component

Well, you tell the suggester what field to use in the first place in the configuration. But I don't quite understand. Suggester is not _intended_ to return documents. It returns, well, suggestions. It's up to you to do something with them, i.e. substitute them into a new query (agains

Quick quester about suggester component

I've setup the suggester and want to act on the full document when user selects one of the suggestions. Ideally it would be nice to be able to tell the suggester to return more than just the field that the suggestion index is built from. If that can't be done, then should I do the

Suggester highlighter offsets inaccurate

Hello, I am using Solr 6.6's Suggester functionality to power an autosuggest widget that returns lists of people's names. One requirement that we have is that the suggester be punctuation-insensitive. For example, entering: 'Dr Joh' should provide the suggestion 'Dr

Solr suggester query with quotes produces different results

Hi guys, I have the Suggester configured using the FreeTextFactory. Noticed that if I dont use quotation marks, I only get single term results. If i use quotation marks around my query, then I only get results that are comprised of multiple terms. There is no configuration that would return both

Re: Suggester and fuzzy/infix suggestions

he current collection. - --- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Suggester-and-fuzzy-infix-suggestions-tp4343225p4343382.html Sent from the Solr - Use

Re: Suggester and fuzzy/infix suggestions

I can keep the top weighted suggestions. >> >> wunder >> Walter Underwood >> wun...@wunderwood.org >> http://observer.wunderwood.org/ (my blog) >> >> >>> On Jun 28, 2017, at 9:47 AM, Student 1 wrote: >>> >>> Hi, >>&g

Re: Suggester and fuzzy/infix suggestions

org/ (my blog) > > > > On Jun 28, 2017, at 9:47 AM, Student 1 wrote: > > > > Hi, > > > > I'm trying to implement suggestions mechanism using Solr Suggester > > component, that would work like this: > > > > - look inside of the field

Re: Suggester and fuzzy/infix suggestions

://observer.wunderwood.org/ (my blog) > On Jun 28, 2017, at 9:47 AM, Student 1 wrote: > > Hi, > > I'm trying to implement suggestions mechanism using Solr Suggester > component, that would work like this: > > - look inside of the field (like AnalyzingInfixLookupFa

Suggester and fuzzy/infix suggestions

Hi, I'm trying to implement suggestions mechanism using Solr Suggester component, that would work like this: - look inside of the field (like AnalyzingInfixLookupFactory does) AND - allow for minor spelling mistakes (like FuzzyLookupFactory does). Is it at all possible? It looks to me, lik

Re: SOLR Suggester returns either the full field value or single terms only

ideo g\"":{"numFound":10,"suggestions":[{"term":"g eo","weight":952090016707589760,"payload":""},{"term":"g em","weight":297528130221121792,"payload":""},{"term"

Re: SOLR Suggester returns either the full field value or single terms only

heers - --- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/SOLR-Suggester-returns-either-the-full-field-value-or-single-terms-only-tp4342763p4342987.html Sent from the Solr - Use

Re: SOLR Suggester returns either the full field value or single terms only

hi Alessandro, Thanks very much. I've read your article - which is really great by the way! , and configured my suggester in the following way: mySuggester FreeTextLookupFactory DocumentDictionaryFactory content_suggest true

Re: SOLR Suggester returns either the full field value or single terms only

ro Benedetti > Search Consultant, R&D Software Engineer, Director > Sease Ltd. - www.sease.io > -- > View this message in context: http://lucene.472066.n3. > nabble.com/SOLR-Suggester-returns-either-the-full-field- > value-or-single-terms-only-tp4342763p4342807.html > Sent from the Solr - User mailing list archive at Nabble.com. >

  1   2   3   4   5   6   >