lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Rutherglen <jason.rutherg...@gmail.com>
Subject Re: Auto Suggest
Date Sat, 04 Sep 2010 14:27:29 GMT
Luke,

Thanks.  What happens if there are 3 terms?  It seems like the entire
query can go into facet.prefix?

On Fri, Sep 3, 2010 at 8:05 AM, Luke Tebbs <luke@staffing-systems.co.uk> wrote:
> What about if you do something like this? -
>
> facet=true&facet.mincount=1&q=apple&facet.limit=10&facet.prefix=mou&facet.field=term_suggest&qt=basic&wt=javabin&rows=0&version=1
>
>
> Jason Rutherglen wrote:
>>
>> To clarify, the query analyzer returns that.  Variations such as
>> "apple mou" also do not return anything.  Maybe Jay can comment and
>> then we can amend the article?
>>
>> On Fri, Sep 3, 2010 at 6:12 AM, Jason Rutherglen
>> <jason.rutherglen@gmail.com> wrote:
>>
>>>
>>> Analysis returns "app mou".
>>>
>>> On Thu, Sep 2, 2010 at 6:12 PM, Lance Norskog <goksron@gmail.com> wrote:
>>>
>>>>
>>>> What does analysis.jsp show?
>>>>
>>>> On Thu, Sep 2, 2010 at 5:53 AM, Jason Rutherglen
>>>> <jason.rutherglen@gmail.com> wrote:
>>>>
>>>>>
>>>>> I'm having a different issue with the EdgeNGram technique described
>>>>> here:
>>>>> http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
>>>>>
>>>>> That is one word queries q=app on the query_text field, work fine
>>>>> however "q=app mou" do not.  Why would this be or is there a
>>>>> configuration that could be missing?
>>>>>
>>>>> On Wed, Sep 1, 2010 at 3:53 PM, Eric Grobler
>>>>> <impalaherd@googlemail.com> wrote:
>>>>>
>>>>>>
>>>>>> Thanks for your feedback Robert,
>>>>>>
>>>>>> I will try that and see how Solr performs on my data - I think I
will
>>>>>> create
>>>>>> a field that contains only important key/product terms from the text.
>>>>>>
>>>>>> Regards
>>>>>> Johan
>>>>>>
>>>>>> On Wed, Sep 1, 2010 at 9:12 PM, Robert Petersen <robertpe@buy.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> We don't have that many, just a hundred thousand, and solr response
>>>>>>> times (since the index's docs are small and not complex) are
logged
>>>>>>> as
>>>>>>> typically 1 ms if not 0 ms.  It's funny but sometimes it is
so fast
>>>>>>> no
>>>>>>> milliseconds have elapsed.  Incredible if you ask me...  :)
>>>>>>>
>>>>>>> Once you get SOLR to consider the whole phrase as just one big
term,
>>>>>>> the
>>>>>>> wildcard is very fast.
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Eric Grobler [mailto:impalaherd@googlemail.com]
>>>>>>> Sent: Wednesday, September 01, 2010 12:35 PM
>>>>>>> To: solr-user@lucene.apache.org
>>>>>>> Subject: Re: Auto Suggest
>>>>>>>
>>>>>>> Hi Robert,
>>>>>>>
>>>>>>> Interesting approach, how many documents do you have in Solr?
>>>>>>> I have about 2 million and I just wonder if it might be a bit
slow.
>>>>>>>
>>>>>>> Regards
>>>>>>> Johan
>>>>>>>
>>>>>>> On Wed, Sep 1, 2010 at 7:38 PM, Robert Petersen <robertpe@buy.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> I do this by replacing the spaces with a '%' in a separate
search
>>>>>>>>
>>>>>>>
>>>>>>> field
>>>>>>>
>>>>>>>>
>>>>>>>> which is not parsed nor tokenized and then you can wildcard
across
>>>>>>>> the
>>>>>>>> whole phrase like you want and the spaces don't mess you
up.  Just
>>>>>>>>
>>>>>>>
>>>>>>> store
>>>>>>>
>>>>>>>>
>>>>>>>> the original phrase with spaces in a separate field for returning
to
>>>>>>>>
>>>>>>>
>>>>>>> the
>>>>>>>
>>>>>>>>
>>>>>>>> front end for display.
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Jazz Globe [mailto:jazzglobe@hotmail.com]
>>>>>>>> Sent: Wednesday, September 01, 2010 7:33 AM
>>>>>>>> To: solr-user@lucene.apache.org
>>>>>>>> Subject: Auto Suggest
>>>>>>>>
>>>>>>>>
>>>>>>>> Hallo
>>>>>>>>
>>>>>>>> How would one implement a multiple term auto-suggest feature
in Solr
>>>>>>>> that is filter sensitive?
>>>>>>>> For example, a user enters :
>>>>>>>> "mp3"
>>>>>>>>  and solr might suggest:
>>>>>>>>  ->   "mp3 player"
>>>>>>>>  ->   "mp3 nano"
>>>>>>>>  ->   "mp3 sony"
>>>>>>>> and then the user starts the second word :
>>>>>>>> "mp3 n"
>>>>>>>> and that narrows it down to:
>>>>>>>>  -> "mp3 nano"
>>>>>>>>
>>>>>>>> I had a quick look at the Terms Component.
>>>>>>>> I suppose it just returns term totals for the entire index
and
>>>>>>>> cannot
>>>>>>>>
>>>>>>>
>>>>>>> be
>>>>>>>
>>>>>>>>
>>>>>>>> used with a filter or query?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Johan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>> --
>>>> Lance Norskog
>>>> goksron@gmail.com
>>>>
>>>>
>
>

Mime
View raw message