You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by JMill <ap...@googlemail.com> on 2013/09/24 20:01:40 UTC
Implementing Solr Suggester for Autocomplete (multiple columns)
Hi,
I'm using Solr's Suggester function to implement an autocomplete feature.
I have it setup to check against the "username" and "name" fields. Problem
is when running a query against the name, the second term, after
whitespace (surename) returns 0 results. Works if if query is a partial
name starting from the begining e.g. Given the name "Bill Rogers", a query
for Rogers will return 0 results whereas a query for "Bill" will return
positive (Bill Rogers). As for the username, it's not working at.
I am after the following behaviour.
Match any partial words in the fields "username" or "name" and return the
results. If there is match in the field "name" the return the whole name
e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
single word that was a match)".
schema.xml extract
..
<field name="username" type="text_general" indexed="true" stored="true" />
<field name="name" type="text_general" indexed="true" stored="true"/>
<field name="autocomplete" type="textSpell" indexed="true" stored="false"
multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
...
<copyField source="username" dest="autocomplete"/>
<copyField source="name" dest="autocomplete"/>
...
<fieldType class="solr.TextField" name="textSpell"
positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.StandardTokenizerFactory"/>
<filter class="solr.StandardFilterFactory"/>
<filter class="solr.LowerCaseFilterFactory"/>
</analyzer>
</fieldType>
solrconfig.xml
....
<lst name="spellchecker">
<str name="name">suggest</str>
<str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
<str
name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
<str name="field">autocomplete</str> <!-- the indexed field to derive
suggestions from -->
<float name="threshold">0.005</float>
<str name="buildOnCommit">true</str>
<!--
<str name="sourceLocation">american-english</str>
-->
</lst>
</searchComponent>
..
<requestHandler class="org.apache.solr.handler.component.SearchHandler"
name="/suggest">
<lst name="defaults">
<str name="spellcheck">true</str>
<str name="spellcheck.dictionary">suggest</str>
<str name="spellcheck.onlyMorePopular">true</str>
<str name="spellcheck.count">5</str>
<str name="spellcheck.collate">true</str>
</lst>
<arr name="components">
<str>spellcheck</str>
</arr>
</requestHandler>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
Thanks.
On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> I've used a separated core for storing suggestions, based on what I see
> in: https://github.com/cominvent/autocomplete. You can check the blog
> post on
> www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
> This is really flexible, on the downside it does not use the suggester
> component su this are like regular queries against a separated core.
>
> Greetings!
>
> ----- Mensaje original -----
> De: "Erick Erickson" <er...@gmail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
>
> I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
> index (untokenized) something like
> Bill|Bill Rogers
> Rogers|Bill Rogers
>
> Your suggester then is a simple term lookup (see TermsComponent)
> which is quite fast. What you _don't_ get is autocorrect. But if you
> use terms.prefix, you can also control whether it's whole word match
> or not. To get whole-word in the above, you would set your prefix to
> "Rogers|" for instance. Or you may want to leave off the "|" to see
> more of an autocomplete-type response.
>
> Then, of course, when you display this you need to only display what's
> after the "|" (or whatever delimiter you use).
>
> One other note, this will be case sensitive, so you probably want to
> do casing yourself, index things like
> rogers|Bill Rogers
> and lowercase what you send in to terms component.
>
> Best,
> Erick
>
>
>
> On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com>
> wrote:
> > Hi,
> >
> > I'm using Solr's Suggester function to implement an autocomplete feature.
> > I have it setup to check against the "username" and "name" fields.
> Problem
> > is when running a query against the name, the second term, after
> > whitespace (surename) returns 0 results. Works if if query is a partial
> > name starting from the begining e.g. Given the name "Bill Rogers", a
> query
> > for Rogers will return 0 results whereas a query for "Bill" will return
> > positive (Bill Rogers). As for the username, it's not working at.
> >
> > I am after the following behaviour.
> >
> > Match any partial words in the fields "username" or "name" and return the
> > results. If there is match in the field "name" the return the whole name
> > e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> > single word that was a match)".
> >
> > schema.xml extract
> > ..
> > <field name="username" type="text_general" indexed="true" stored="true"
> />
> > <field name="name" type="text_general" indexed="true" stored="true"/>
> > <field name="autocomplete" type="textSpell" indexed="true" stored="false"
> > multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> > ...
> > <copyField source="username" dest="autocomplete"/>
> > <copyField source="name" dest="autocomplete"/>
> > ...
> >
> > <fieldType class="solr.TextField" name="textSpell"
> > positionIncrementGap="100">
> > <analyzer>
> > <tokenizer class="solr.StandardTokenizerFactory"/>
> > <filter class="solr.StandardFilterFactory"/>
> > <filter class="solr.LowerCaseFilterFactory"/>
> > </analyzer>
> > </fieldType>
> >
> >
> > solrconfig.xml
> >
> > ....
> > <lst name="spellchecker">
> > <str name="name">suggest</str>
> > <str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> > <str
> > name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> > <str name="field">autocomplete</str> <!-- the indexed field to derive
> > suggestions from -->
> > <float name="threshold">0.005</float>
> > <str name="buildOnCommit">true</str>
> > <!--
> > <str name="sourceLocation">american-english</str>
> > -->
> > </lst>
> >
> > </searchComponent>
> >
> > ..
> > <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> > name="/suggest">
> > <lst name="defaults">
> > <str name="spellcheck">true</str>
> > <str name="spellcheck.dictionary">suggest</str>
> > <str name="spellcheck.onlyMorePopular">true</str>
> > <str name="spellcheck.count">5</str>
> > <str name="spellcheck.collate">true</str>
> > </lst>
> > <arr name="components">
> > <str>spellcheck</str>
> > </arr>
> > </requestHandler>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
Posted by Stefan Matheis <ma...@gmail.com>.
That is because of jQuery's changes ..
jQuery.browser (http://api.jquery.com/jQuery.browser/)
Description: Contains flags for the useragent, read from navigator.userAgent. This property was removed in jQuery 1.9 and is available only through the jQuery.migrate plugin. Please try to use feature detection instead.
Those plugins (like autocomplete, for example) normally have version dependencies to jQuery .. to ensure their functionality
-Stefan
On Thursday, September 26, 2013 at 2:50 PM, JMill wrote:
> I managed to get rid of the query error by playing jquery file in the
> velocity folder and adding line: "<script type="text/javascript"
> src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
> That has not solved the issues the console is showing a new error -
> "[13:42:55.181] TypeError: $.browser is undefined @
> http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90".
> Any ideas?
>
>
> On Thu, Sep 26, 2013 at 1:12 PM, JMill <apprentice321@googlemail.com (mailto:apprentice321@googlemail.com)> wrote:
>
> > Do you know the directory the "#{url_root}" in <script
> > type="text/javascript" src="#{url_root}/js/lib/
> > jquery-1.7.2.min.js"></script> points too? and same for ""#{url_for_solr}"
> > <script type="text/javascript"
> > src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
> >
> >
> > On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > jlbetancourt@uci.cu (mailto:jlbetancourt@uci.cu)> wrote:
> >
> > > Try quering the core where the data has been imported, something like:
> > >
> > > http://localhost:8983/solr/suggestions/select?q=uc
> > >
> > > In the previous URL suggestions is the name I give to the core, so this
> > > should change, if you get results, then the problem could be the jquery
> > > dependency. I don't remember doing any change, as far as I know that js
> > > file is bundled with solr (at leat in 3.x) version perhaps you could change
> > > it the correct jquery version on solr 4.4, if you go into the admin panel
> > > (in solr 3.6):
> > >
> > > http://localhost:8983/solr/admin/schema.jsp
> > >
> > > And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
> > > loaded in solr 4.4 it should load a similar file, but perhaps a more recent
> > > version.
> > >
> > > Perhaps you could change that part to something like:
> > >
> > > <script type="text/javascript"
> > > src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
> > >
> > > Which is used at least on a solr 4.1 that I have laying aroud here
> > > somewhere.
> > >
> > > In any case you can test the suggestions using the URL that I suggest on
> > > the top of this mail, in that case you should be able to see the possible
> > > results, of course in a less fancy way.
> > >
> > > ----- Mensaje original -----
> > > De: "JMill" <apprentice321@googlemail.com (mailto:apprentice321@googlemail.com)>
> > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
> > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > columns)
> > >
> > > Could it be the jquery library that is the problem? I opened up
> > > solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
> > > the jquery library but I can't seem to find the directory referenced,
> > > line: <script type="text/javascript"
> > > src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
> > > "#{url_for_solr}" points to?
> > >
> > >
> > > On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> > > jlbetancourt@uci.cu (mailto:jlbetancourt@uci.cu)> wrote:
> > > > Perhaps this could be an issue, I know that this works perfectly in solr
> > >
> > > 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
> > > some tests, but what have been done in that core should work in solr 4.4,
> > > perhaps there is a setting that need some tweaking but it's impossible of
> > > knowing without checking the logs. In case that any incompatibility is
> > > present it should pop out on the logs.
> > > >
> > > > Regards,
> > > >
> > > > ----- Mensaje original -----
> > > > De: "JMill" <apprentice321@googlemail.com (mailto:apprentice321@googlemail.com)>
> > > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > > Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
> > > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > >
> > >
> > > columns)
> > > >
> > > > I simple query through admin (*:*) confirms the data is exists. The
> > > version
> > > > I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
> > > > wonder of this is the problem?
> > > >
> > > >
> > > > On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > > > jlbetancourt@uci.cu (mailto:jlbetancourt@uci.cu)> wrote:
> > > >
> > > > > The response does not show any error, can you confirm that the data is
> > > in
> > > > > solr? you should be able to see the numDoc stats in the admin UI. Which
> > > > > version of Solr are you using? I believe that the example was tested on
> > > > > Solr 3.x at least at the time I use it.
> > > > >
> > > > > Regards,
> > > > >
> > > > > ----- Mensaje original -----
> > > > > De: "JMill" <apprentice321@googlemail.com (mailto:apprentice321@googlemail.com)>
> > > > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > > > Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
> > > > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > > >
> > > >
> > >
> > > columns)
> > > > >
> > > > > I followed the instructions, I am able to browse to "
> > > > > http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am
> > > > >
> > > >
> > >
> > > not
> > > > > getting any suggestions (typed in c in Find Textbox).
> > > > >
> > > > > I wonder if loading the example data is the problem? The response I
> > > get
> > > > > after executing the script "feed-ac.sh (http://feed-ac.sh)" (step 3) is the following.
> > > > >
> > > > > user$ ./feed-ac.sh (http://feed-ac.sh)
> > > > > <?xml version="1.0" encoding="UTF-8"?>
> > > > > <response>
> > > > > <lst name="responseHeader"><int name="status">0</int><int
> > > > > name="QTime">2239</int></lst>
> > > > > </response>
> > > > >
> > > > > Are you able to confirm if this the expected response?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > > > > jlbetancourt@uci.cu (mailto:jlbetancourt@uci.cu)> wrote:
> > > > >
> > > > > > I've used a separated core for storing suggestions, based on what I
> > > see
> > > > > > in: https://github.com/cominvent/autocomplete. You can check the
> > > > >
> > > >
> > >
> > > blog
> > > > > > post on
> > > > > > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/ (http://www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/).
> > > > > > This is really flexible, on the downside it does not use the
> > > > > >
> > > > >
> > > >
> > >
> > > suggester
> > > > > > component su this are like regular queries against a separated core.
> > > > > >
> > > > > > Greetings!
> > > > > >
> > > > > > ----- Mensaje original -----
> > > > > > De: "Erick Erickson" <erickerickson@gmail.com (mailto:erickerickson@gmail.com)>
> > > > > > Para: solr-user@lucene.apache.org (mailto:solr-user@lucene.apache.org)
> > > > > > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> > > > > > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> > > > > >
> > > > >
> > > > > columns)
> > > > > >
> > > > > > I've sometimes seen this handled by clever tokenizing. For "Bill
> > > Rogers",
> > > > > > index (untokenized) something like
> > > > > > Bill|Bill Rogers
> > > > > > Rogers|Bill Rogers
> > > > > >
> > > > > > Your suggester then is a simple term lookup (see TermsComponent)
> > > > > > which is quite fast. What you _don't_ get is autocorrect. But if you
> > > > > > use terms.prefix, you can also control whether it's whole word match
> > > > > > or not. To get whole-word in the above, you would set your prefix to
> > > > > > "Rogers|" for instance. Or you may want to leave off the "|" to see
> > > > > > more of an autocomplete-type response.
> > > > > >
> > > > > > Then, of course, when you display this you need to only display
> > > what's
> > > > > > after the "|" (or whatever delimiter you use).
> > > > > >
> > > > > > One other note, this will be case sensitive, so you probably want to
> > > > > > do casing yourself, index things like
> > > > > > rogers|Bill Rogers
> > > > > > and lowercase what you send in to terms component.
> > > > > >
> > > > > > Best,
> > > > > > Erick
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
> > >
> > >
> > > ________________________________________________________________________________________________
> > > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > > del 2014. Ver www.uci.cu (http://www.uci.cu)
> > >
> > >
> > > ________________________________________________________________________________________________
> > > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > > del 2014. Ver www.uci.cu (http://www.uci.cu)
> > >
> >
> >
>
>
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
I forgot to mention you could check the boost section on the configuration file of the core to see how your suggestions will be ranked, basically the boost factor for each field allows you to decide which suggestion do you like to come first, perhaps in your app you could keep track of how much a suggestion given to a user is actually used as the query and boost this suggestions as is more likely to become a query for the user; thinking a little ahead this could improve your user experience and additionally low the load on your server, because if a suggestion given to a high number of users become a query, this query should already be in the cache. This are just thoughts but I hope could be useful to you.
Regards,
----- Mensaje original -----
De: "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>
Para: solr-user@lucene.apache.org
Enviados: Viernes, 27 de Septiembre 2013 19:44:28
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Actually I don't use that field, it could be used to do some form of basic collaborative filtering, so you could use a high value for items in your collection that you want to come first, but in my case this was not a requirement and I don't use it at all.
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Viernes, 27 de Septiembre 2013 16:19:40
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I am not sure about the value to use for the option "popularity". Is there
a method or do you just go with some arbitrary number?
On Thursday, September 26, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Great!! I haven't see your message yet, perhaps you could create a PR to
that Github repository, son it will be in sync with current versions of
Solr.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Jueves, 26 de Septiembre 2013 9:10:49
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> solved.
>
>
> On Thu, Sep 26, 2013 at 1:50 PM, JMill <ap...@googlemail.com>
wrote:
>
>> I managed to get rid of the query error by playing jquery file in the
>> velocity folder and adding line: "<script type="text/javascript"
>>
src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
>> That has not solved the issues the console is showing a new error -
>> "[13:42:55.181] TypeError: $.browser is undefined @
>>
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90
".
>> Any ideas?
>>
>>
>> On Thu, Sep 26, 2013 at 1:12 PM, JMill <apprentice321@googlemail.com
>wrote:
>>
>>> Do you know the directory the "#{url_root}" in <script
>>> type="text/javascript" src="#{url_root}/js/lib/
>>> jquery-1.7.2.min.js"></script> points too? and same for
>>> ""#{url_for_solr}" <script type="text/javascript"
>>> src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>>> Try quering the core where the data has been imported, something like:
>>>>
>>>> http://localhost:8983/solr/suggestions/select?q=uc
>>>>
>>>> In the previous URL suggestions is the name I give to the core, so this
>>>> should change, if you get results, then the problem could be the jquery
>>>> dependency. I don't remember doing any change, as far as I know that js
>>>> file is bundled with solr (at leat in 3.x) version perhaps you could
change
>>>> it the correct jquery version on solr 4.4, if you go into the admin
panel
>>>> (in solr 3.6):
>>>>
>>>> http://localhost:8983/solr/admin/schema.jsp
>>>>
>>>> And inspect the loaded code, the required file (jquery-1.4.2.min.js)
>>>> gets loaded in solr 4.4 it should load a similar file, but perhaps a
more
>>>> recent version.
>>>>
>>>> Perhaps you could change that part to something like:
>>>>
>>>> <script type="text/javascript"
>>>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>>>
>>>> Which is used at least on a solr 4.1 that I have laying aroud here
>>>> somewhere.
>>>>
>>>> In any case you can test the suggestions using the URL that I suggest
on
>>>> the top of this mail, in that case you should be able to see the
possible
>>>> results, of course in a less fancy way.
>>>>
>>>> ----- Mensaje original -----
>>>> De: "JMill" <ap...@googlemail.com>
>>>> Para: solr-user@lucene.apache.org
>>>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>>> columns)
>>>>
>>>> Could it be the jquery library that is the problem? I opened up
>>>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
>>>> to
>>>> the jquery library but I can't seem to find the directory referenced,
>>>> line: <script type="text/javascript"
>>>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>>>> "#{url_for_solr}" points to?
>>>>
>>>>
>>>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
Actually I don't use that field, it could be used to do some form of basic collaborative filtering, so you could use a high value for items in your collection that you want to come first, but in my case this was not a requirement and I don't use it at all.
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Viernes, 27 de Septiembre 2013 16:19:40
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I am not sure about the value to use for the option "popularity". Is there
a method or do you just go with some arbitrary number?
On Thursday, September 26, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Great!! I haven't see your message yet, perhaps you could create a PR to
that Github repository, son it will be in sync with current versions of
Solr.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Jueves, 26 de Septiembre 2013 9:10:49
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> solved.
>
>
> On Thu, Sep 26, 2013 at 1:50 PM, JMill <ap...@googlemail.com>
wrote:
>
>> I managed to get rid of the query error by playing jquery file in the
>> velocity folder and adding line: "<script type="text/javascript"
>>
src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
>> That has not solved the issues the console is showing a new error -
>> "[13:42:55.181] TypeError: $.browser is undefined @
>>
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90
".
>> Any ideas?
>>
>>
>> On Thu, Sep 26, 2013 at 1:12 PM, JMill <apprentice321@googlemail.com
>wrote:
>>
>>> Do you know the directory the "#{url_root}" in <script
>>> type="text/javascript" src="#{url_root}/js/lib/
>>> jquery-1.7.2.min.js"></script> points too? and same for
>>> ""#{url_for_solr}" <script type="text/javascript"
>>> src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>>> Try quering the core where the data has been imported, something like:
>>>>
>>>> http://localhost:8983/solr/suggestions/select?q=uc
>>>>
>>>> In the previous URL suggestions is the name I give to the core, so this
>>>> should change, if you get results, then the problem could be the jquery
>>>> dependency. I don't remember doing any change, as far as I know that js
>>>> file is bundled with solr (at leat in 3.x) version perhaps you could
change
>>>> it the correct jquery version on solr 4.4, if you go into the admin
panel
>>>> (in solr 3.6):
>>>>
>>>> http://localhost:8983/solr/admin/schema.jsp
>>>>
>>>> And inspect the loaded code, the required file (jquery-1.4.2.min.js)
>>>> gets loaded in solr 4.4 it should load a similar file, but perhaps a
more
>>>> recent version.
>>>>
>>>> Perhaps you could change that part to something like:
>>>>
>>>> <script type="text/javascript"
>>>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>>>
>>>> Which is used at least on a solr 4.1 that I have laying aroud here
>>>> somewhere.
>>>>
>>>> In any case you can test the suggestions using the URL that I suggest
on
>>>> the top of this mail, in that case you should be able to see the
possible
>>>> results, of course in a less fancy way.
>>>>
>>>> ----- Mensaje original -----
>>>> De: "JMill" <ap...@googlemail.com>
>>>> Para: solr-user@lucene.apache.org
>>>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>>> columns)
>>>>
>>>> Could it be the jquery library that is the problem? I opened up
>>>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
>>>> to
>>>> the jquery library but I can't seem to find the directory referenced,
>>>> line: <script type="text/javascript"
>>>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>>>> "#{url_for_solr}" points to?
>>>>
>>>>
>>>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
I am not sure about the value to use for the option "popularity". Is there
a method or do you just go with some arbitrary number?
On Thursday, September 26, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Great!! I haven't see your message yet, perhaps you could create a PR to
that Github repository, son it will be in sync with current versions of
Solr.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Jueves, 26 de Septiembre 2013 9:10:49
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> solved.
>
>
> On Thu, Sep 26, 2013 at 1:50 PM, JMill <ap...@googlemail.com>
wrote:
>
>> I managed to get rid of the query error by playing jquery file in the
>> velocity folder and adding line: "<script type="text/javascript"
>>
src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
>> That has not solved the issues the console is showing a new error -
>> "[13:42:55.181] TypeError: $.browser is undefined @
>>
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90
".
>> Any ideas?
>>
>>
>> On Thu, Sep 26, 2013 at 1:12 PM, JMill <apprentice321@googlemail.com
>wrote:
>>
>>> Do you know the directory the "#{url_root}" in <script
>>> type="text/javascript" src="#{url_root}/js/lib/
>>> jquery-1.7.2.min.js"></script> points too? and same for
>>> ""#{url_for_solr}" <script type="text/javascript"
>>> src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>>> Try quering the core where the data has been imported, something like:
>>>>
>>>> http://localhost:8983/solr/suggestions/select?q=uc
>>>>
>>>> In the previous URL suggestions is the name I give to the core, so this
>>>> should change, if you get results, then the problem could be the jquery
>>>> dependency. I don't remember doing any change, as far as I know that js
>>>> file is bundled with solr (at leat in 3.x) version perhaps you could
change
>>>> it the correct jquery version on solr 4.4, if you go into the admin
panel
>>>> (in solr 3.6):
>>>>
>>>> http://localhost:8983/solr/admin/schema.jsp
>>>>
>>>> And inspect the loaded code, the required file (jquery-1.4.2.min.js)
>>>> gets loaded in solr 4.4 it should load a similar file, but perhaps a
more
>>>> recent version.
>>>>
>>>> Perhaps you could change that part to something like:
>>>>
>>>> <script type="text/javascript"
>>>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>>>
>>>> Which is used at least on a solr 4.1 that I have laying aroud here
>>>> somewhere.
>>>>
>>>> In any case you can test the suggestions using the URL that I suggest
on
>>>> the top of this mail, in that case you should be able to see the
possible
>>>> results, of course in a less fancy way.
>>>>
>>>> ----- Mensaje original -----
>>>> De: "JMill" <ap...@googlemail.com>
>>>> Para: solr-user@lucene.apache.org
>>>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>>> columns)
>>>>
>>>> Could it be the jquery library that is the problem? I opened up
>>>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
>>>> to
>>>> the jquery library but I can't seem to find the directory referenced,
>>>> line: <script type="text/javascript"
>>>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>>>> "#{url_for_solr}" points to?
>>>>
>>>>
>>>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
Great!! I haven't see your message yet, perhaps you could create a PR to that Github repository, son it will be in sync with current versions of Solr.
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Jueves, 26 de Septiembre 2013 9:10:49
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
solved.
On Thu, Sep 26, 2013 at 1:50 PM, JMill <ap...@googlemail.com> wrote:
> I managed to get rid of the query error by playing jquery file in the
> velocity folder and adding line: "<script type="text/javascript"
> src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
> That has not solved the issues the console is showing a new error -
> "[13:42:55.181] TypeError: $.browser is undefined @
> http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90".
> Any ideas?
>
>
> On Thu, Sep 26, 2013 at 1:12 PM, JMill <ap...@googlemail.com>wrote:
>
>> Do you know the directory the "#{url_root}" in <script
>> type="text/javascript" src="#{url_root}/js/lib/
>> jquery-1.7.2.min.js"></script> points too? and same for
>> ""#{url_for_solr}" <script type="text/javascript"
>> src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
>>
>>
>> On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>
>>> Try quering the core where the data has been imported, something like:
>>>
>>> http://localhost:8983/solr/suggestions/select?q=uc
>>>
>>> In the previous URL suggestions is the name I give to the core, so this
>>> should change, if you get results, then the problem could be the jquery
>>> dependency. I don't remember doing any change, as far as I know that js
>>> file is bundled with solr (at leat in 3.x) version perhaps you could change
>>> it the correct jquery version on solr 4.4, if you go into the admin panel
>>> (in solr 3.6):
>>>
>>> http://localhost:8983/solr/admin/schema.jsp
>>>
>>> And inspect the loaded code, the required file (jquery-1.4.2.min.js)
>>> gets loaded in solr 4.4 it should load a similar file, but perhaps a more
>>> recent version.
>>>
>>> Perhaps you could change that part to something like:
>>>
>>> <script type="text/javascript"
>>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>>
>>> Which is used at least on a solr 4.1 that I have laying aroud here
>>> somewhere.
>>>
>>> In any case you can test the suggestions using the URL that I suggest on
>>> the top of this mail, in that case you should be able to see the possible
>>> results, of course in a less fancy way.
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> columns)
>>>
>>> Could it be the jquery library that is the problem? I opened up
>>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
>>> to
>>> the jquery library but I can't seem to find the directory referenced,
>>> line: <script type="text/javascript"
>>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>>> "#{url_for_solr}" points to?
>>>
>>>
>>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>> > Perhaps this could be an issue, I know that this works perfectly in
>>> solr
>>> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to
>>> do
>>> some tests, but what have been done in that core should work in solr 4.4,
>>> perhaps there is a setting that need some tweaking but it's impossible of
>>> knowing without checking the logs. In case that any incompatibility is
>>> present it should pop out on the logs.
>>> >
>>> > Regards,
>>> >
>>> > ----- Mensaje original -----
>>> > De: "JMill" <ap...@googlemail.com>
>>> > Para: solr-user@lucene.apache.org
>>> > Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>>> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> columns)
>>> >
>>> > I simple query through admin (*:*) confirms the data is exists. The
>>> version
>>> > I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x.
>>> I
>>> > wonder of this is the problem?
>>> >
>>> >
>>> > On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> > jlbetancourt@uci.cu> wrote:
>>> >
>>> >> The response does not show any error, can you confirm that the data
>>> is in
>>> >> solr? you should be able to see the numDoc stats in the admin UI.
>>> Which
>>> >> version of Solr are you using? I believe that the example was tested
>>> on
>>> >> Solr 3.x at least at the time I use it.
>>> >>
>>> >> Regards,
>>> >>
>>> >> ----- Mensaje original -----
>>> >> De: "JMill" <ap...@googlemail.com>
>>> >> Para: solr-user@lucene.apache.org
>>> >> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>>> >> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> columns)
>>> >>
>>> >> I followed the instructions, I am able to browse to "
>>> >> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am
>>> not
>>> >> getting any suggestions (typed in c in Find Textbox).
>>> >>
>>> >> I wonder if loading the example data is the problem? The response I
>>> get
>>> >> after executing the script "feed-ac.sh" (step 3) is the following.
>>> >>
>>> >> user$ ./feed-ac.sh
>>> >> <?xml version="1.0" encoding="UTF-8"?>
>>> >> <response>
>>> >> <lst name="responseHeader"><int name="status">0</int><int
>>> >> name="QTime">2239</int></lst>
>>> >> </response>
>>> >>
>>> >> Are you able to confirm if this the expected response?
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> >> jlbetancourt@uci.cu> wrote:
>>> >>
>>> >> > I've used a separated core for storing suggestions, based on what I
>>> see
>>> >> > in: https://github.com/cominvent/autocomplete. You can check the
>>> blog
>>> >> > post on
>>> >> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/
>>> .
>>> >> > This is really flexible, on the downside it does not use the
>>> suggester
>>> >> > component su this are like regular queries against a separated core.
>>> >> >
>>> >> > Greetings!
>>> >> >
>>> >> > ----- Mensaje original -----
>>> >> > De: "Erick Erickson" <er...@gmail.com>
>>> >> > Para: solr-user@lucene.apache.org
>>> >> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
>>> >> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> >> columns)
>>> >> >
>>> >> > I've sometimes seen this handled by clever tokenizing. For "Bill
>>> Rogers",
>>> >> > index (untokenized) something like
>>> >> > Bill|Bill Rogers
>>> >> > Rogers|Bill Rogers
>>> >> >
>>> >> > Your suggester then is a simple term lookup (see TermsComponent)
>>> >> > which is quite fast. What you _don't_ get is autocorrect. But if you
>>> >> > use terms.prefix, you can also control whether it's whole word match
>>> >> > or not. To get whole-word in the above, you would set your prefix to
>>> >> > "Rogers|" for instance. Or you may want to leave off the "|" to see
>>> >> > more of an autocomplete-type response.
>>> >> >
>>> >> > Then, of course, when you display this you need to only display
>>> what's
>>> >> > after the "|" (or whatever delimiter you use).
>>> >> >
>>> >> > One other note, this will be case sensitive, so you probably want to
>>> >> > do casing yourself, index things like
>>> >> > rogers|Bill Rogers
>>> >> > and lowercase what you send in to terms component.
>>> >> >
>>> >> > Best,
>>> >> > Erick
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
>>>
>>>
>>> ________________________________________________________________________________________________
>>> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
>>> del 2014. Ver www.uci.cu
>>>
>>>
>>> ________________________________________________________________________________________________
>>> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
>>> del 2014. Ver www.uci.cu
>>>
>>
>>
>
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
solved.
On Thu, Sep 26, 2013 at 1:50 PM, JMill <ap...@googlemail.com> wrote:
> I managed to get rid of the query error by playing jquery file in the
> velocity folder and adding line: "<script type="text/javascript"
> src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
> That has not solved the issues the console is showing a new error -
> "[13:42:55.181] TypeError: $.browser is undefined @
> http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90".
> Any ideas?
>
>
> On Thu, Sep 26, 2013 at 1:12 PM, JMill <ap...@googlemail.com>wrote:
>
>> Do you know the directory the "#{url_root}" in <script
>> type="text/javascript" src="#{url_root}/js/lib/
>> jquery-1.7.2.min.js"></script> points too? and same for
>> ""#{url_for_solr}" <script type="text/javascript"
>> src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
>>
>>
>> On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>
>>> Try quering the core where the data has been imported, something like:
>>>
>>> http://localhost:8983/solr/suggestions/select?q=uc
>>>
>>> In the previous URL suggestions is the name I give to the core, so this
>>> should change, if you get results, then the problem could be the jquery
>>> dependency. I don't remember doing any change, as far as I know that js
>>> file is bundled with solr (at leat in 3.x) version perhaps you could change
>>> it the correct jquery version on solr 4.4, if you go into the admin panel
>>> (in solr 3.6):
>>>
>>> http://localhost:8983/solr/admin/schema.jsp
>>>
>>> And inspect the loaded code, the required file (jquery-1.4.2.min.js)
>>> gets loaded in solr 4.4 it should load a similar file, but perhaps a more
>>> recent version.
>>>
>>> Perhaps you could change that part to something like:
>>>
>>> <script type="text/javascript"
>>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>>
>>> Which is used at least on a solr 4.1 that I have laying aroud here
>>> somewhere.
>>>
>>> In any case you can test the suggestions using the URL that I suggest on
>>> the top of this mail, in that case you should be able to see the possible
>>> results, of course in a less fancy way.
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> columns)
>>>
>>> Could it be the jquery library that is the problem? I opened up
>>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
>>> to
>>> the jquery library but I can't seem to find the directory referenced,
>>> line: <script type="text/javascript"
>>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>>> "#{url_for_solr}" points to?
>>>
>>>
>>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>> > Perhaps this could be an issue, I know that this works perfectly in
>>> solr
>>> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to
>>> do
>>> some tests, but what have been done in that core should work in solr 4.4,
>>> perhaps there is a setting that need some tweaking but it's impossible of
>>> knowing without checking the logs. In case that any incompatibility is
>>> present it should pop out on the logs.
>>> >
>>> > Regards,
>>> >
>>> > ----- Mensaje original -----
>>> > De: "JMill" <ap...@googlemail.com>
>>> > Para: solr-user@lucene.apache.org
>>> > Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>>> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> columns)
>>> >
>>> > I simple query through admin (*:*) confirms the data is exists. The
>>> version
>>> > I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x.
>>> I
>>> > wonder of this is the problem?
>>> >
>>> >
>>> > On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> > jlbetancourt@uci.cu> wrote:
>>> >
>>> >> The response does not show any error, can you confirm that the data
>>> is in
>>> >> solr? you should be able to see the numDoc stats in the admin UI.
>>> Which
>>> >> version of Solr are you using? I believe that the example was tested
>>> on
>>> >> Solr 3.x at least at the time I use it.
>>> >>
>>> >> Regards,
>>> >>
>>> >> ----- Mensaje original -----
>>> >> De: "JMill" <ap...@googlemail.com>
>>> >> Para: solr-user@lucene.apache.org
>>> >> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>>> >> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> columns)
>>> >>
>>> >> I followed the instructions, I am able to browse to "
>>> >> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am
>>> not
>>> >> getting any suggestions (typed in c in Find Textbox).
>>> >>
>>> >> I wonder if loading the example data is the problem? The response I
>>> get
>>> >> after executing the script "feed-ac.sh" (step 3) is the following.
>>> >>
>>> >> user$ ./feed-ac.sh
>>> >> <?xml version="1.0" encoding="UTF-8"?>
>>> >> <response>
>>> >> <lst name="responseHeader"><int name="status">0</int><int
>>> >> name="QTime">2239</int></lst>
>>> >> </response>
>>> >>
>>> >> Are you able to confirm if this the expected response?
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> >> jlbetancourt@uci.cu> wrote:
>>> >>
>>> >> > I've used a separated core for storing suggestions, based on what I
>>> see
>>> >> > in: https://github.com/cominvent/autocomplete. You can check the
>>> blog
>>> >> > post on
>>> >> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/
>>> .
>>> >> > This is really flexible, on the downside it does not use the
>>> suggester
>>> >> > component su this are like regular queries against a separated core.
>>> >> >
>>> >> > Greetings!
>>> >> >
>>> >> > ----- Mensaje original -----
>>> >> > De: "Erick Erickson" <er...@gmail.com>
>>> >> > Para: solr-user@lucene.apache.org
>>> >> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
>>> >> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>>> >> columns)
>>> >> >
>>> >> > I've sometimes seen this handled by clever tokenizing. For "Bill
>>> Rogers",
>>> >> > index (untokenized) something like
>>> >> > Bill|Bill Rogers
>>> >> > Rogers|Bill Rogers
>>> >> >
>>> >> > Your suggester then is a simple term lookup (see TermsComponent)
>>> >> > which is quite fast. What you _don't_ get is autocorrect. But if you
>>> >> > use terms.prefix, you can also control whether it's whole word match
>>> >> > or not. To get whole-word in the above, you would set your prefix to
>>> >> > "Rogers|" for instance. Or you may want to leave off the "|" to see
>>> >> > more of an autocomplete-type response.
>>> >> >
>>> >> > Then, of course, when you display this you need to only display
>>> what's
>>> >> > after the "|" (or whatever delimiter you use).
>>> >> >
>>> >> > One other note, this will be case sensitive, so you probably want to
>>> >> > do casing yourself, index things like
>>> >> > rogers|Bill Rogers
>>> >> > and lowercase what you send in to terms component.
>>> >> >
>>> >> > Best,
>>> >> > Erick
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
>>>
>>>
>>> ________________________________________________________________________________________________
>>> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
>>> del 2014. Ver www.uci.cu
>>>
>>>
>>> ________________________________________________________________________________________________
>>> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
>>> del 2014. Ver www.uci.cu
>>>
>>
>>
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
I managed to get rid of the query error by playing jquery file in the
velocity folder and adding line: "<script type="text/javascript"
src="#{url_for_solr}/admin/file?file=/velocity/jquery.min.js&contentType=text/javascript"></script>".
That has not solved the issues the console is showing a new error -
"[13:42:55.181] TypeError: $.browser is undefined @
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.js&contentType=text/javascript:90".
Any ideas?
On Thu, Sep 26, 2013 at 1:12 PM, JMill <ap...@googlemail.com> wrote:
> Do you know the directory the "#{url_root}" in <script
> type="text/javascript" src="#{url_root}/js/lib/
> jquery-1.7.2.min.js"></script> points too? and same for ""#{url_for_solr}"
> <script type="text/javascript"
> src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
>
>
> On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>
>> Try quering the core where the data has been imported, something like:
>>
>> http://localhost:8983/solr/suggestions/select?q=uc
>>
>> In the previous URL suggestions is the name I give to the core, so this
>> should change, if you get results, then the problem could be the jquery
>> dependency. I don't remember doing any change, as far as I know that js
>> file is bundled with solr (at leat in 3.x) version perhaps you could change
>> it the correct jquery version on solr 4.4, if you go into the admin panel
>> (in solr 3.6):
>>
>> http://localhost:8983/solr/admin/schema.jsp
>>
>> And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
>> loaded in solr 4.4 it should load a similar file, but perhaps a more recent
>> version.
>>
>> Perhaps you could change that part to something like:
>>
>> <script type="text/javascript"
>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>
>> Which is used at least on a solr 4.1 that I have laying aroud here
>> somewhere.
>>
>> In any case you can test the suggestions using the URL that I suggest on
>> the top of this mail, in that case you should be able to see the possible
>> results, of course in a less fancy way.
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>>
>> Could it be the jquery library that is the problem? I opened up
>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
>> the jquery library but I can't seem to find the directory referenced,
>> line: <script type="text/javascript"
>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>> "#{url_for_solr}" points to?
>>
>>
>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>> > Perhaps this could be an issue, I know that this works perfectly in solr
>> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
>> some tests, but what have been done in that core should work in solr 4.4,
>> perhaps there is a setting that need some tweaking but it's impossible of
>> knowing without checking the logs. In case that any incompatibility is
>> present it should pop out on the logs.
>> >
>> > Regards,
>> >
>> > ----- Mensaje original -----
>> > De: "JMill" <ap...@googlemail.com>
>> > Para: solr-user@lucene.apache.org
>> > Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>> >
>> > I simple query through admin (*:*) confirms the data is exists. The
>> version
>> > I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
>> > wonder of this is the problem?
>> >
>> >
>> > On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> > jlbetancourt@uci.cu> wrote:
>> >
>> >> The response does not show any error, can you confirm that the data is
>> in
>> >> solr? you should be able to see the numDoc stats in the admin UI. Which
>> >> version of Solr are you using? I believe that the example was tested on
>> >> Solr 3.x at least at the time I use it.
>> >>
>> >> Regards,
>> >>
>> >> ----- Mensaje original -----
>> >> De: "JMill" <ap...@googlemail.com>
>> >> Para: solr-user@lucene.apache.org
>> >> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>> >> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>> >>
>> >> I followed the instructions, I am able to browse to "
>> >> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am
>> not
>> >> getting any suggestions (typed in c in Find Textbox).
>> >>
>> >> I wonder if loading the example data is the problem? The response I
>> get
>> >> after executing the script "feed-ac.sh" (step 3) is the following.
>> >>
>> >> user$ ./feed-ac.sh
>> >> <?xml version="1.0" encoding="UTF-8"?>
>> >> <response>
>> >> <lst name="responseHeader"><int name="status">0</int><int
>> >> name="QTime">2239</int></lst>
>> >> </response>
>> >>
>> >> Are you able to confirm if this the expected response?
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> >> jlbetancourt@uci.cu> wrote:
>> >>
>> >> > I've used a separated core for storing suggestions, based on what I
>> see
>> >> > in: https://github.com/cominvent/autocomplete. You can check the
>> blog
>> >> > post on
>> >> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
>> >> > This is really flexible, on the downside it does not use the
>> suggester
>> >> > component su this are like regular queries against a separated core.
>> >> >
>> >> > Greetings!
>> >> >
>> >> > ----- Mensaje original -----
>> >> > De: "Erick Erickson" <er...@gmail.com>
>> >> > Para: solr-user@lucene.apache.org
>> >> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
>> >> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> >> columns)
>> >> >
>> >> > I've sometimes seen this handled by clever tokenizing. For "Bill
>> Rogers",
>> >> > index (untokenized) something like
>> >> > Bill|Bill Rogers
>> >> > Rogers|Bill Rogers
>> >> >
>> >> > Your suggester then is a simple term lookup (see TermsComponent)
>> >> > which is quite fast. What you _don't_ get is autocorrect. But if you
>> >> > use terms.prefix, you can also control whether it's whole word match
>> >> > or not. To get whole-word in the above, you would set your prefix to
>> >> > "Rogers|" for instance. Or you may want to leave off the "|" to see
>> >> > more of an autocomplete-type response.
>> >> >
>> >> > Then, of course, when you display this you need to only display
>> what's
>> >> > after the "|" (or whatever delimiter you use).
>> >> >
>> >> > One other note, this will be case sensitive, so you probably want to
>> >> > do casing yourself, index things like
>> >> > rogers|Bill Rogers
>> >> > and lowercase what you send in to terms component.
>> >> >
>> >> > Best,
>> >> > Erick
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
>>
>>
>> ________________________________________________________________________________________________
>> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
>> del 2014. Ver www.uci.cu
>>
>>
>> ________________________________________________________________________________________________
>> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
>> del 2014. Ver www.uci.cu
>>
>
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
Do you know the directory the "#{url_root}" in <script
type="text/javascript" src="#{url_root}/js/lib/
jquery-1.7.2.min.js"></script> points too? and same for ""#{url_for_solr}"
<script type="text/javascript"
src="#{url_for_solr}/js/lib/jquery-1.7.2.min.js"></script>
On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Try quering the core where the data has been imported, something like:
>
> http://localhost:8983/solr/suggestions/select?q=uc
>
> In the previous URL suggestions is the name I give to the core, so this
> should change, if you get results, then the problem could be the jquery
> dependency. I don't remember doing any change, as far as I know that js
> file is bundled with solr (at leat in 3.x) version perhaps you could change
> it the correct jquery version on solr 4.4, if you go into the admin panel
> (in solr 3.6):
>
> http://localhost:8983/solr/admin/schema.jsp
>
> And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
> loaded in solr 4.4 it should load a similar file, but perhaps a more recent
> version.
>
> Perhaps you could change that part to something like:
>
> <script type="text/javascript"
> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>
> Which is used at least on a solr 4.1 that I have laying aroud here
> somewhere.
>
> In any case you can test the suggestions using the URL that I suggest on
> the top of this mail, in that case you should be able to see the possible
> results, of course in a less fancy way.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
>
> Could it be the jquery library that is the problem? I opened up
> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
> the jquery library but I can't seem to find the directory referenced,
> line: <script type="text/javascript"
> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
> "#{url_for_solr}" points to?
>
>
> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
> > Perhaps this could be an issue, I know that this works perfectly in solr
> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
> some tests, but what have been done in that core should work in solr 4.4,
> perhaps there is a setting that need some tweaking but it's impossible of
> knowing without checking the logs. In case that any incompatibility is
> present it should pop out on the logs.
> >
> > Regards,
> >
> > ----- Mensaje original -----
> > De: "JMill" <ap...@googlemail.com>
> > Para: solr-user@lucene.apache.org
> > Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
> >
> > I simple query through admin (*:*) confirms the data is exists. The
> version
> > I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
> > wonder of this is the problem?
> >
> >
> > On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
> > jlbetancourt@uci.cu> wrote:
> >
> >> The response does not show any error, can you confirm that the data is
> in
> >> solr? you should be able to see the numDoc stats in the admin UI. Which
> >> version of Solr are you using? I believe that the example was tested on
> >> Solr 3.x at least at the time I use it.
> >>
> >> Regards,
> >>
> >> ----- Mensaje original -----
> >> De: "JMill" <ap...@googlemail.com>
> >> Para: solr-user@lucene.apache.org
> >> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
> >> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
> >>
> >> I followed the instructions, I am able to browse to "
> >> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
> >> getting any suggestions (typed in c in Find Textbox).
> >>
> >> I wonder if loading the example data is the problem? The response I get
> >> after executing the script "feed-ac.sh" (step 3) is the following.
> >>
> >> user$ ./feed-ac.sh
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <response>
> >> <lst name="responseHeader"><int name="status">0</int><int
> >> name="QTime">2239</int></lst>
> >> </response>
> >>
> >> Are you able to confirm if this the expected response?
> >>
> >>
> >>
> >>
> >> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
> >> jlbetancourt@uci.cu> wrote:
> >>
> >> > I've used a separated core for storing suggestions, based on what I
> see
> >> > in: https://github.com/cominvent/autocomplete. You can check the blog
> >> > post on
> >> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
> >> > This is really flexible, on the downside it does not use the suggester
> >> > component su this are like regular queries against a separated core.
> >> >
> >> > Greetings!
> >> >
> >> > ----- Mensaje original -----
> >> > De: "Erick Erickson" <er...@gmail.com>
> >> > Para: solr-user@lucene.apache.org
> >> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> >> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> >> columns)
> >> >
> >> > I've sometimes seen this handled by clever tokenizing. For "Bill
> Rogers",
> >> > index (untokenized) something like
> >> > Bill|Bill Rogers
> >> > Rogers|Bill Rogers
> >> >
> >> > Your suggester then is a simple term lookup (see TermsComponent)
> >> > which is quite fast. What you _don't_ get is autocorrect. But if you
> >> > use terms.prefix, you can also control whether it's whole word match
> >> > or not. To get whole-word in the above, you would set your prefix to
> >> > "Rogers|" for instance. Or you may want to leave off the "|" to see
> >> > more of an autocomplete-type response.
> >> >
> >> > Then, of course, when you display this you need to only display what's
> >> > after the "|" (or whatever delimiter you use).
> >> >
> >> > One other note, this will be case sensitive, so you probably want to
> >> > do casing yourself, index things like
> >> > rogers|Bill Rogers
> >> > and lowercase what you send in to terms component.
> >> >
> >> > Best,
> >> > Erick
> >> >
> >> >
> >> >
> >> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
I guess we found the culprit.
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> That's and indication that jQuery can't be loaded, and without jQuery the
autocomplete plugin won't work. This plugin is used to show the popup list
that show up at the bottom of the input.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 15:40:00
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> Not yet but I do see the "$" not found in console.
>
> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>> As far as I can tell it is. You can check that by seeing the Console logs
> on your browser (chrome, firefox, etc.). There should be an error saying
> that the $ function it's not found. In any case I'll try to set up a
> testing environment here, but I can only use solr 4.1, which I have here.
I
> haven't downloaded/tested the 4.4 version yet. Do you try replacing the
> line that includes the jquery-1.4.3.min.js with the new one?
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 14:44:53
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>
>> That seems to work. I get back an xml containing a bunch of suggestions.
>> Can we agree that it's jquery that's the problem?
>>
>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>> Try quering the core where the data has been imported, something like:
>>>
>>> http://localhost:8983/solr/suggestions/select?q=uc
>>>
>>> In the previous URL suggestions is the name I give to the core, so this
>> should change, if you get results, then the problem could be the jquery
>> dependency. I don't remember doing any change, as far as I know that js
>> file is bundled with solr (at leat in 3.x) version perhaps you could
> change
>> it the correct jquery version on solr 4.4, if you go into the admin panel
>> (in solr 3.6):
>>>
>>> http://localhost:8983/solr/admin/schema.jsp
>>>
>>> And inspect the loaded code, the required file (jquery-1.4.2.min.js)
gets
>> loaded in solr 4.4 it should load a similar file, but perhaps a more
> recent
>> version.
>>>
>>> Perhaps you could change that part to something like:
>>>
>>> <script type="text/javascript"
>> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>>
>>> Which is used at least on a solr 4.1 that I have laying aroud here
>> somewhere.
>>>
>>> In any case you can test the suggestions using the URL that I suggest on
>> the top of this mail, in that case you should be able to see the possible
>> results, of course in a less fancy way.
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>>>
>>> Could it be the jquery library that is the problem? I opened up
>>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
> to
>>> the jquery library but I can't seem to find the directory referenced,
>>> line: <script type="text/javascript"
>>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>>> "#{url_for_solr}" points to?
>>>
>>>
>>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>> Perhaps this could be an issue, I know that this works perfectly in
solr
>>> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to
> do
>>> some tests, but what have been done in that core should work in solr
4.4,
>>> perhaps there is a setting that need some tweaking but it's impossible
of
>>> knowing without checking the logs. In case
that________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
del 2014. Ver www.uci.cu
>
>
________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
del 2014. Ver www.uci.cu
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
That's and indication that jQuery can't be loaded, and without jQuery the autocomplete plugin won't work. This plugin is used to show the popup list that show up at the bottom of the input.
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 15:40:00
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Not yet but I do see the "$" not found in console.
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> As far as I can tell it is. You can check that by seeing the Console logs
on your browser (chrome, firefox, etc.). There should be an error saying
that the $ function it's not found. In any case I'll try to set up a
testing environment here, but I can only use solr 4.1, which I have here. I
haven't downloaded/tested the 4.4 version yet. Do you try replacing the
line that includes the jquery-1.4.3.min.js with the new one?
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 14:44:53
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> That seems to work. I get back an xml containing a bunch of suggestions.
> Can we agree that it's jquery that's the problem?
>
> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>> Try quering the core where the data has been imported, something like:
>>
>> http://localhost:8983/solr/suggestions/select?q=uc
>>
>> In the previous URL suggestions is the name I give to the core, so this
> should change, if you get results, then the problem could be the jquery
> dependency. I don't remember doing any change, as far as I know that js
> file is bundled with solr (at leat in 3.x) version perhaps you could
change
> it the correct jquery version on solr 4.4, if you go into the admin panel
> (in solr 3.6):
>>
>> http://localhost:8983/solr/admin/schema.jsp
>>
>> And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
> loaded in solr 4.4 it should load a similar file, but perhaps a more
recent
> version.
>>
>> Perhaps you could change that part to something like:
>>
>> <script type="text/javascript"
> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>
>> Which is used at least on a solr 4.1 that I have laying aroud here
> somewhere.
>>
>> In any case you can test the suggestions using the URL that I suggest on
> the top of this mail, in that case you should be able to see the possible
> results, of course in a less fancy way.
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>
>> Could it be the jquery library that is the problem? I opened up
>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
to
>> the jquery library but I can't seem to find the directory referenced,
>> line: <script type="text/javascript"
>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>> "#{url_for_solr}" points to?
>>
>>
>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>> Perhaps this could be an issue, I know that this works perfectly in solr
>> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to
do
>> some tests, but what have been done in that core should work in solr 4.4,
>> perhaps there is a setting that need some tweaking but it's impossible of
>> knowing without checking the logs. In case that any incompatibility is
>> present it should pop out on the logs.
>>>
>>> Regards,
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>>>
>>> I simple query through admin (*:*) confirms the data is exists. The
>> version
>>> I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
>>> wonder of this is the problem?
>>>
>>>
>>> On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>>> The response does not show any error, can you confirm that the data is
> in
>>>> solr? you should be able to see the numDoc stats in the admin UI. Which
>>>> version of Solr are you using? I believe that the example was tested on
>>>> Solr 3.x at least at the time I use it.
>>>>
>
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
Not yet but I do see the "$" not found in console.
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> As far as I can tell it is. You can check that by seeing the Console logs
on your browser (chrome, firefox, etc.). There should be an error saying
that the $ function it's not found. In any case I'll try to set up a
testing environment here, but I can only use solr 4.1, which I have here. I
haven't downloaded/tested the 4.4 version yet. Do you try replacing the
line that includes the jquery-1.4.3.min.js with the new one?
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 14:44:53
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> That seems to work. I get back an xml containing a bunch of suggestions.
> Can we agree that it's jquery that's the problem?
>
> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>> Try quering the core where the data has been imported, something like:
>>
>> http://localhost:8983/solr/suggestions/select?q=uc
>>
>> In the previous URL suggestions is the name I give to the core, so this
> should change, if you get results, then the problem could be the jquery
> dependency. I don't remember doing any change, as far as I know that js
> file is bundled with solr (at leat in 3.x) version perhaps you could
change
> it the correct jquery version on solr 4.4, if you go into the admin panel
> (in solr 3.6):
>>
>> http://localhost:8983/solr/admin/schema.jsp
>>
>> And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
> loaded in solr 4.4 it should load a similar file, but perhaps a more
recent
> version.
>>
>> Perhaps you could change that part to something like:
>>
>> <script type="text/javascript"
> src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>>
>> Which is used at least on a solr 4.1 that I have laying aroud here
> somewhere.
>>
>> In any case you can test the suggestions using the URL that I suggest on
> the top of this mail, in that case you should be able to see the possible
> results, of course in a less fancy way.
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>
>> Could it be the jquery library that is the problem? I opened up
>> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
to
>> the jquery library but I can't seem to find the directory referenced,
>> line: <script type="text/javascript"
>> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
>> "#{url_for_solr}" points to?
>>
>>
>> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>> Perhaps this could be an issue, I know that this works perfectly in solr
>> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to
do
>> some tests, but what have been done in that core should work in solr 4.4,
>> perhaps there is a setting that need some tweaking but it's impossible of
>> knowing without checking the logs. In case that any incompatibility is
>> present it should pop out on the logs.
>>>
>>> Regards,
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>>>
>>> I simple query through admin (*:*) confirms the data is exists. The
>> version
>>> I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
>>> wonder of this is the problem?
>>>
>>>
>>> On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>>> The response does not show any error, can you confirm that the data is
> in
>>>> solr? you should be able to see the numDoc stats in the admin UI. Which
>>>> version of Solr are you using? I believe that the example was tested on
>>>> Solr 3.x at least at the time I use it.
>>>>
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
As far as I can tell it is. You can check that by seeing the Console logs on your browser (chrome, firefox, etc.). There should be an error saying that the $ function it's not found. In any case I'll try to set up a testing environment here, but I can only use solr 4.1, which I have here. I haven't downloaded/tested the 4.4 version yet. Do you try replacing the line that includes the jquery-1.4.3.min.js with the new one?
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 14:44:53
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
That seems to work. I get back an xml containing a bunch of suggestions.
Can we agree that it's jquery that's the problem?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Try quering the core where the data has been imported, something like:
>
> http://localhost:8983/solr/suggestions/select?q=uc
>
> In the previous URL suggestions is the name I give to the core, so this
should change, if you get results, then the problem could be the jquery
dependency. I don't remember doing any change, as far as I know that js
file is bundled with solr (at leat in 3.x) version perhaps you could change
it the correct jquery version on solr 4.4, if you go into the admin panel
(in solr 3.6):
>
> http://localhost:8983/solr/admin/schema.jsp
>
> And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
loaded in solr 4.4 it should load a similar file, but perhaps a more recent
version.
>
> Perhaps you could change that part to something like:
>
> <script type="text/javascript"
src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>
> Which is used at least on a solr 4.1 that I have laying aroud here
somewhere.
>
> In any case you can test the suggestions using the URL that I suggest on
the top of this mail, in that case you should be able to see the possible
results, of course in a less fancy way.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> Could it be the jquery library that is the problem? I opened up
> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
> the jquery library but I can't seem to find the directory referenced,
> line: <script type="text/javascript"
> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
> "#{url_for_solr}" points to?
>
>
> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>> Perhaps this could be an issue, I know that this works perfectly in solr
> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
> some tests, but what have been done in that core should work in solr 4.4,
> perhaps there is a setting that need some tweaking but it's impossible of
> knowing without checking the logs. In case that any incompatibility is
> present it should pop out on the logs.
>>
>> Regards,
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>
>> I simple query through admin (*:*) confirms the data is exists. The
> version
>> I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
>> wonder of this is the problem?
>>
>>
>> On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>
>>> The response does not show any error, can you confirm that the data is
in
>>> solr? you should be able to see the numDoc stats in the admin UI. Which
>>> version of Solr are you using? I believe that the example was tested on
>>> Solr 3.x at least at the time I use it.
>>>
>>> Regards,
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>>
>>> I followed the instructions, I am able to browse to "
>>> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
>>> getting any suggestions (typed in c in Find Textbox).
>>>
>>> I wonder if loading the example data is the problem? The response I get
>>> after executing the script "feed-ac.sh" (step 3) is the following.
>>>
>>> user$ ./feed-ac.sh
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <response>
>>> <lst name="responseHeader"><int name="status">0</int><int
>>> name="QTime">2239</int></lst>
>>> </response>
>>>
>>> Are you able to confirm if this the expected response?
>>>
>>>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>> > I've used a separated core for storing suggestions, based on what I
see
>>> > in: https://github.com/cominvent/autocomplete. You can check the blog
>>> > post on
>>> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
>>> > This is really flexible, on the downside it does not use the suggester
>>> > component su this are like regular queries against a separated core.
>>> >
>>> > Greetings!
>>> >
>
________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
del 2014. Ver www.uci.cu
>
>
________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
del 2014. Ver www.uci.cu
>
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
That seems to work. I get back an xml containing a bunch of suggestions.
Can we agree that it's jquery that's the problem?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Try quering the core where the data has been imported, something like:
>
> http://localhost:8983/solr/suggestions/select?q=uc
>
> In the previous URL suggestions is the name I give to the core, so this
should change, if you get results, then the problem could be the jquery
dependency. I don't remember doing any change, as far as I know that js
file is bundled with solr (at leat in 3.x) version perhaps you could change
it the correct jquery version on solr 4.4, if you go into the admin panel
(in solr 3.6):
>
> http://localhost:8983/solr/admin/schema.jsp
>
> And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets
loaded in solr 4.4 it should load a similar file, but perhaps a more recent
version.
>
> Perhaps you could change that part to something like:
>
> <script type="text/javascript"
src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
>
> Which is used at least on a solr 4.1 that I have laying aroud here
somewhere.
>
> In any case you can test the suggestions using the URL that I suggest on
the top of this mail, in that case you should be able to see the possible
results, of course in a less fancy way.
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> Could it be the jquery library that is the problem? I opened up
> solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
> the jquery library but I can't seem to find the directory referenced,
> line: <script type="text/javascript"
> src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
> "#{url_for_solr}" points to?
>
>
> On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>> Perhaps this could be an issue, I know that this works perfectly in solr
> 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
> some tests, but what have been done in that core should work in solr 4.4,
> perhaps there is a setting that need some tweaking but it's impossible of
> knowing without checking the logs. In case that any incompatibility is
> present it should pop out on the logs.
>>
>> Regards,
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>
>> I simple query through admin (*:*) confirms the data is exists. The
> version
>> I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
>> wonder of this is the problem?
>>
>>
>> On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>
>>> The response does not show any error, can you confirm that the data is
in
>>> solr? you should be able to see the numDoc stats in the admin UI. Which
>>> version of Solr are you using? I believe that the example was tested on
>>> Solr 3.x at least at the time I use it.
>>>
>>> Regards,
>>>
>>> ----- Mensaje original -----
>>> De: "JMill" <ap...@googlemail.com>
>>> Para: solr-user@lucene.apache.org
>>> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
>>>
>>> I followed the instructions, I am able to browse to "
>>> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
>>> getting any suggestions (typed in c in Find Textbox).
>>>
>>> I wonder if loading the example data is the problem? The response I get
>>> after executing the script "feed-ac.sh" (step 3) is the following.
>>>
>>> user$ ./feed-ac.sh
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <response>
>>> <lst name="responseHeader"><int name="status">0</int><int
>>> name="QTime">2239</int></lst>
>>> </response>
>>>
>>> Are you able to confirm if this the expected response?
>>>
>>>
>>>
>>>
>>> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>>> jlbetancourt@uci.cu> wrote:
>>>
>>> > I've used a separated core for storing suggestions, based on what I
see
>>> > in: https://github.com/cominvent/autocomplete. You can check the blog
>>> > post on
>>> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
>>> > This is really flexible, on the downside it does not use the suggester
>>> > component su this are like regular queries against a separated core.
>>> >
>>> > Greetings!
>>> >
>
________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
del 2014. Ver www.uci.cu
>
>
________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
del 2014. Ver www.uci.cu
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
Try quering the core where the data has been imported, something like:
http://localhost:8983/solr/suggestions/select?q=uc
In the previous URL suggestions is the name I give to the core, so this should change, if you get results, then the problem could be the jquery dependency. I don't remember doing any change, as far as I know that js file is bundled with solr (at leat in 3.x) version perhaps you could change it the correct jquery version on solr 4.4, if you go into the admin panel (in solr 3.6):
http://localhost:8983/solr/admin/schema.jsp
And inspect the loaded code, the required file (jquery-1.4.2.min.js) gets loaded in solr 4.4 it should load a similar file, but perhaps a more recent version.
Perhaps you could change that part to something like:
<script type="text/javascript" src="#{url_root}/js/lib/jquery-1.7.2.min.js"></script>
Which is used at least on a solr 4.1 that I have laying aroud here somewhere.
In any case you can test the suggestions using the URL that I suggest on the top of this mail, in that case you should be able to see the possible results, of course in a less fancy way.
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Could it be the jquery library that is the problem? I opened up
solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
the jquery library but I can't seem to find the directory referenced,
line: <script type="text/javascript"
src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
"#{url_for_solr}" points to?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Perhaps this could be an issue, I know that this works perfectly in solr
3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
some tests, but what have been done in that core should work in solr 4.4,
perhaps there is a setting that need some tweaking but it's impossible of
knowing without checking the logs. In case that any incompatibility is
present it should pop out on the logs.
>
> Regards,
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> I simple query through admin (*:*) confirms the data is exists. The
version
> I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
> wonder of this is the problem?
>
>
> On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>
>> The response does not show any error, can you confirm that the data is in
>> solr? you should be able to see the numDoc stats in the admin UI. Which
>> version of Solr are you using? I believe that the example was tested on
>> Solr 3.x at least at the time I use it.
>>
>> Regards,
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>>
>> I followed the instructions, I am able to browse to "
>> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
>> getting any suggestions (typed in c in Find Textbox).
>>
>> I wonder if loading the example data is the problem? The response I get
>> after executing the script "feed-ac.sh" (step 3) is the following.
>>
>> user$ ./feed-ac.sh
>> <?xml version="1.0" encoding="UTF-8"?>
>> <response>
>> <lst name="responseHeader"><int name="status">0</int><int
>> name="QTime">2239</int></lst>
>> </response>
>>
>> Are you able to confirm if this the expected response?
>>
>>
>>
>>
>> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>
>> > I've used a separated core for storing suggestions, based on what I see
>> > in: https://github.com/cominvent/autocomplete. You can check the blog
>> > post on
>> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
>> > This is really flexible, on the downside it does not use the suggester
>> > component su this are like regular queries against a separated core.
>> >
>> > Greetings!
>> >
>> > ----- Mensaje original -----
>> > De: "Erick Erickson" <er...@gmail.com>
>> > Para: solr-user@lucene.apache.org
>> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
>> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>> >
>> > I've sometimes seen this handled by clever tokenizing. For "Bill
Rogers",
>> > index (untokenized) something like
>> > Bill|Bill Rogers
>> > Rogers|Bill Rogers
>> >
>> > Your suggester then is a simple term lookup (see TermsComponent)
>> > which is quite fast. What you _don't_ get is autocorrect. But if you
>> > use terms.prefix, you can also control whether it's whole word match
>> > or not. To get whole-word in the above, you would set your prefix to
>> > "Rogers|" for instance. Or you may want to leave off the "|" to see
>> > more of an autocomplete-type response.
>> >
>> > Then, of course, when you display this you need to only display what's
>> > after the "|" (or whatever delimiter you use).
>> >
>> > One other note, this will be case sensitive, so you probably want to
>> > do casing yourself, index things like
>> > rogers|Bill Rogers
>> > and lowercase what you send in to terms component.
>> >
>> > Best,
>> > Erick
>> >
>> >
>> >
>> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
Could it be the jquery library that is the problem? I opened up
solr-home/ac/conf/velocity/head.vm with an editor and I see a reference to
the jquery library but I can't seem to find the directory referenced,
line: <script type="text/javascript"
src="#{url_for_solr}/admin/jquery-1.4.3.min.js">. Do you know where
"#{url_for_solr}" points to?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> Perhaps this could be an issue, I know that this works perfectly in solr
3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do
some tests, but what have been done in that core should work in solr 4.4,
perhaps there is a setting that need some tweaking but it's impossible of
knowing without checking the logs. In case that any incompatibility is
present it should pop out on the logs.
>
> Regards,
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>
> I simple query through admin (*:*) confirms the data is exists. The
version
> I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
> wonder of this is the problem?
>
>
> On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>
>> The response does not show any error, can you confirm that the data is in
>> solr? you should be able to see the numDoc stats in the admin UI. Which
>> version of Solr are you using? I believe that the example was tested on
>> Solr 3.x at least at the time I use it.
>>
>> Regards,
>>
>> ----- Mensaje original -----
>> De: "JMill" <ap...@googlemail.com>
>> Para: solr-user@lucene.apache.org
>> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
>> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
>>
>> I followed the instructions, I am able to browse to "
>> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
>> getting any suggestions (typed in c in Find Textbox).
>>
>> I wonder if loading the example data is the problem? The response I get
>> after executing the script "feed-ac.sh" (step 3) is the following.
>>
>> user$ ./feed-ac.sh
>> <?xml version="1.0" encoding="UTF-8"?>
>> <response>
>> <lst name="responseHeader"><int name="status">0</int><int
>> name="QTime">2239</int></lst>
>> </response>
>>
>> Are you able to confirm if this the expected response?
>>
>>
>>
>>
>> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
>> jlbetancourt@uci.cu> wrote:
>>
>> > I've used a separated core for storing suggestions, based on what I see
>> > in: https://github.com/cominvent/autocomplete. You can check the blog
>> > post on
>> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
>> > This is really flexible, on the downside it does not use the suggester
>> > component su this are like regular queries against a separated core.
>> >
>> > Greetings!
>> >
>> > ----- Mensaje original -----
>> > De: "Erick Erickson" <er...@gmail.com>
>> > Para: solr-user@lucene.apache.org
>> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
>> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
>> columns)
>> >
>> > I've sometimes seen this handled by clever tokenizing. For "Bill
Rogers",
>> > index (untokenized) something like
>> > Bill|Bill Rogers
>> > Rogers|Bill Rogers
>> >
>> > Your suggester then is a simple term lookup (see TermsComponent)
>> > which is quite fast. What you _don't_ get is autocorrect. But if you
>> > use terms.prefix, you can also control whether it's whole word match
>> > or not. To get whole-word in the above, you would set your prefix to
>> > "Rogers|" for instance. Or you may want to leave off the "|" to see
>> > more of an autocomplete-type response.
>> >
>> > Then, of course, when you display this you need to only display what's
>> > after the "|" (or whatever delimiter you use).
>> >
>> > One other note, this will be case sensitive, so you probably want to
>> > do casing yourself, index things like
>> > rogers|Bill Rogers
>> > and lowercase what you send in to terms component.
>> >
>> > Best,
>> > Erick
>> >
>> >
>> >
>> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
Perhaps this could be an issue, I know that this works perfectly in solr 3.6 (this is the one I was using). Currently I don't have a solr 4.4 to do some tests, but what have been done in that core should work in solr 4.4, perhaps there is a setting that need some tweaking but it's impossible of knowing without checking the logs. In case that any incompatibility is present it should pop out on the logs.
Regards,
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 11:10:32
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I simple query through admin (*:*) confirms the data is exists. The version
I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
wonder of this is the problem?
On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> The response does not show any error, can you confirm that the data is in
> solr? you should be able to see the numDoc stats in the admin UI. Which
> version of Solr are you using? I believe that the example was tested on
> Solr 3.x at least at the time I use it.
>
> Regards,
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
>
> I followed the instructions, I am able to browse to "
> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
> getting any suggestions (typed in c in Find Textbox).
>
> I wonder if loading the example data is the problem? The response I get
> after executing the script "feed-ac.sh" (step 3) is the following.
>
> user$ ./feed-ac.sh
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader"><int name="status">0</int><int
> name="QTime">2239</int></lst>
> </response>
>
> Are you able to confirm if this the expected response?
>
>
>
>
> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>
> > I've used a separated core for storing suggestions, based on what I see
> > in: https://github.com/cominvent/autocomplete. You can check the blog
> > post on
> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
> > This is really flexible, on the downside it does not use the suggester
> > component su this are like regular queries against a separated core.
> >
> > Greetings!
> >
> > ----- Mensaje original -----
> > De: "Erick Erickson" <er...@gmail.com>
> > Para: solr-user@lucene.apache.org
> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
> >
> > I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
> > index (untokenized) something like
> > Bill|Bill Rogers
> > Rogers|Bill Rogers
> >
> > Your suggester then is a simple term lookup (see TermsComponent)
> > which is quite fast. What you _don't_ get is autocorrect. But if you
> > use terms.prefix, you can also control whether it's whole word match
> > or not. To get whole-word in the above, you would set your prefix to
> > "Rogers|" for instance. Or you may want to leave off the "|" to see
> > more of an autocomplete-type response.
> >
> > Then, of course, when you display this you need to only display what's
> > after the "|" (or whatever delimiter you use).
> >
> > One other note, this will be case sensitive, so you probably want to
> > do casing yourself, index things like
> > rogers|Bill Rogers
> > and lowercase what you send in to terms component.
> >
> > Best,
> > Erick
> >
> >
> >
> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com>
> > wrote:
> > > Hi,
> > >
> > > I'm using Solr's Suggester function to implement an autocomplete
> feature.
> > > I have it setup to check against the "username" and "name" fields.
> > Problem
> > > is when running a query against the name, the second term, after
> > > whitespace (surename) returns 0 results. Works if if query is a
> partial
> > > name starting from the begining e.g. Given the name "Bill Rogers", a
> > query
> > > for Rogers will return 0 results whereas a query for "Bill" will return
> > > positive (Bill Rogers). As for the username, it's not working at.
> > >
> > > I am after the following behaviour.
> > >
> > > Match any partial words in the fields "username" or "name" and return
> the
> > > results. If there is match in the field "name" the return the whole
> name
> > > e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> > > single word that was a match)".
> > >
> > > schema.xml extract
> > > ..
> > > <field name="username" type="text_general" indexed="true" stored="true"
> > />
> > > <field name="name" type="text_general" indexed="true" stored="true"/>
> > > <field name="autocomplete" type="textSpell" indexed="true"
> stored="false"
> > > multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> > > ...
> > > <copyField source="username" dest="autocomplete"/>
> > > <copyField source="name" dest="autocomplete"/>
> > > ...
> > >
> > > <fieldType class="solr.TextField" name="textSpell"
> > > positionIncrementGap="100">
> > > <analyzer>
> > > <tokenizer class="solr.StandardTokenizerFactory"/>
> > > <filter class="solr.StandardFilterFactory"/>
> > > <filter class="solr.LowerCaseFilterFactory"/>
> > > </analyzer>
> > > </fieldType>
> > >
> > >
> > > solrconfig.xml
> > >
> > > ....
> > > <lst name="spellchecker">
> > > <str name="name">suggest</str>
> > > <str
> name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> > > <str
> > > name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> > > <str name="field">autocomplete</str> <!-- the indexed field to
> derive
> > > suggestions from -->
> > > <float name="threshold">0.005</float>
> > > <str name="buildOnCommit">true</str>
> > > <!--
> > > <str name="sourceLocation">american-english</str>
> > > -->
> > > </lst>
> > >
> > > </searchComponent>
> > >
> > > ..
> > > <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> > > name="/suggest">
> > > <lst name="defaults">
> > > <str name="spellcheck">true</str>
> > > <str name="spellcheck.dictionary">suggest</str>
> > > <str name="spellcheck.onlyMorePopular">true</str>
> > > <str name="spellcheck.count">5</str>
> > > <str name="spellcheck.collate">true</str>
> > > </lst>
> > > <arr name="components">
> > > <str>spellcheck</str>
> > > </arr>
> > > </requestHandler>
> >
> >
> ________________________________________________________________________________________________
> > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > del 2014. Ver www.uci.cu
> >
> >
> ________________________________________________________________________________________________
> > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > del 2014. Ver www.uci.cu
> >
>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
I simple query through admin (*:*) confirms the data is exists. The version
I'm working with is solr 4.4.0. The autocomplete manual refers to 3.x. I
wonder of this is the problem?
On Wed, Sep 25, 2013 at 4:01 PM, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> The response does not show any error, can you confirm that the data is in
> solr? you should be able to see the numDoc stats in the admin UI. Which
> version of Solr are you using? I believe that the example was tested on
> Solr 3.x at least at the time I use it.
>
> Regards,
>
> ----- Mensaje original -----
> De: "JMill" <ap...@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
>
> I followed the instructions, I am able to browse to "
> http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
> getting any suggestions (typed in c in Find Textbox).
>
> I wonder if loading the example data is the problem? The response I get
> after executing the script "feed-ac.sh" (step 3) is the following.
>
> user$ ./feed-ac.sh
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader"><int name="status">0</int><int
> name="QTime">2239</int></lst>
> </response>
>
> Are you able to confirm if this the expected response?
>
>
>
>
> On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
> jlbetancourt@uci.cu> wrote:
>
> > I've used a separated core for storing suggestions, based on what I see
> > in: https://github.com/cominvent/autocomplete. You can check the blog
> > post on
> > www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
> > This is really flexible, on the downside it does not use the suggester
> > component su this are like regular queries against a separated core.
> >
> > Greetings!
> >
> > ----- Mensaje original -----
> > De: "Erick Erickson" <er...@gmail.com>
> > Para: solr-user@lucene.apache.org
> > Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> > Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
> columns)
> >
> > I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
> > index (untokenized) something like
> > Bill|Bill Rogers
> > Rogers|Bill Rogers
> >
> > Your suggester then is a simple term lookup (see TermsComponent)
> > which is quite fast. What you _don't_ get is autocorrect. But if you
> > use terms.prefix, you can also control whether it's whole word match
> > or not. To get whole-word in the above, you would set your prefix to
> > "Rogers|" for instance. Or you may want to leave off the "|" to see
> > more of an autocomplete-type response.
> >
> > Then, of course, when you display this you need to only display what's
> > after the "|" (or whatever delimiter you use).
> >
> > One other note, this will be case sensitive, so you probably want to
> > do casing yourself, index things like
> > rogers|Bill Rogers
> > and lowercase what you send in to terms component.
> >
> > Best,
> > Erick
> >
> >
> >
> > On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com>
> > wrote:
> > > Hi,
> > >
> > > I'm using Solr's Suggester function to implement an autocomplete
> feature.
> > > I have it setup to check against the "username" and "name" fields.
> > Problem
> > > is when running a query against the name, the second term, after
> > > whitespace (surename) returns 0 results. Works if if query is a
> partial
> > > name starting from the begining e.g. Given the name "Bill Rogers", a
> > query
> > > for Rogers will return 0 results whereas a query for "Bill" will return
> > > positive (Bill Rogers). As for the username, it's not working at.
> > >
> > > I am after the following behaviour.
> > >
> > > Match any partial words in the fields "username" or "name" and return
> the
> > > results. If there is match in the field "name" the return the whole
> name
> > > e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> > > single word that was a match)".
> > >
> > > schema.xml extract
> > > ..
> > > <field name="username" type="text_general" indexed="true" stored="true"
> > />
> > > <field name="name" type="text_general" indexed="true" stored="true"/>
> > > <field name="autocomplete" type="textSpell" indexed="true"
> stored="false"
> > > multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> > > ...
> > > <copyField source="username" dest="autocomplete"/>
> > > <copyField source="name" dest="autocomplete"/>
> > > ...
> > >
> > > <fieldType class="solr.TextField" name="textSpell"
> > > positionIncrementGap="100">
> > > <analyzer>
> > > <tokenizer class="solr.StandardTokenizerFactory"/>
> > > <filter class="solr.StandardFilterFactory"/>
> > > <filter class="solr.LowerCaseFilterFactory"/>
> > > </analyzer>
> > > </fieldType>
> > >
> > >
> > > solrconfig.xml
> > >
> > > ....
> > > <lst name="spellchecker">
> > > <str name="name">suggest</str>
> > > <str
> name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> > > <str
> > > name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> > > <str name="field">autocomplete</str> <!-- the indexed field to
> derive
> > > suggestions from -->
> > > <float name="threshold">0.005</float>
> > > <str name="buildOnCommit">true</str>
> > > <!--
> > > <str name="sourceLocation">american-english</str>
> > > -->
> > > </lst>
> > >
> > > </searchComponent>
> > >
> > > ..
> > > <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> > > name="/suggest">
> > > <lst name="defaults">
> > > <str name="spellcheck">true</str>
> > > <str name="spellcheck.dictionary">suggest</str>
> > > <str name="spellcheck.onlyMorePopular">true</str>
> > > <str name="spellcheck.count">5</str>
> > > <str name="spellcheck.collate">true</str>
> > > </lst>
> > > <arr name="components">
> > > <str>spellcheck</str>
> > > </arr>
> > > </requestHandler>
> >
> >
> ________________________________________________________________________________________________
> > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > del 2014. Ver www.uci.cu
> >
> >
> ________________________________________________________________________________________________
> > III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> > del 2014. Ver www.uci.cu
> >
>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
The response does not show any error, can you confirm that the data is in solr? you should be able to see the numDoc stats in the admin UI. Which version of Solr are you using? I believe that the example was tested on Solr 3.x at least at the time I use it.
Regards,
----- Mensaje original -----
De: "JMill" <ap...@googlemail.com>
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 10:57:31
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I followed the instructions, I am able to browse to "
http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
getting any suggestions (typed in c in Find Textbox).
I wonder if loading the example data is the problem? The response I get
after executing the script "feed-ac.sh" (step 3) is the following.
user$ ./feed-ac.sh
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int
name="QTime">2239</int></lst>
</response>
Are you able to confirm if this the expected response?
On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> I've used a separated core for storing suggestions, based on what I see
> in: https://github.com/cominvent/autocomplete. You can check the blog
> post on
> www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
> This is really flexible, on the downside it does not use the suggester
> component su this are like regular queries against a separated core.
>
> Greetings!
>
> ----- Mensaje original -----
> De: "Erick Erickson" <er...@gmail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
>
> I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
> index (untokenized) something like
> Bill|Bill Rogers
> Rogers|Bill Rogers
>
> Your suggester then is a simple term lookup (see TermsComponent)
> which is quite fast. What you _don't_ get is autocorrect. But if you
> use terms.prefix, you can also control whether it's whole word match
> or not. To get whole-word in the above, you would set your prefix to
> "Rogers|" for instance. Or you may want to leave off the "|" to see
> more of an autocomplete-type response.
>
> Then, of course, when you display this you need to only display what's
> after the "|" (or whatever delimiter you use).
>
> One other note, this will be case sensitive, so you probably want to
> do casing yourself, index things like
> rogers|Bill Rogers
> and lowercase what you send in to terms component.
>
> Best,
> Erick
>
>
>
> On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com>
> wrote:
> > Hi,
> >
> > I'm using Solr's Suggester function to implement an autocomplete feature.
> > I have it setup to check against the "username" and "name" fields.
> Problem
> > is when running a query against the name, the second term, after
> > whitespace (surename) returns 0 results. Works if if query is a partial
> > name starting from the begining e.g. Given the name "Bill Rogers", a
> query
> > for Rogers will return 0 results whereas a query for "Bill" will return
> > positive (Bill Rogers). As for the username, it's not working at.
> >
> > I am after the following behaviour.
> >
> > Match any partial words in the fields "username" or "name" and return the
> > results. If there is match in the field "name" the return the whole name
> > e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> > single word that was a match)".
> >
> > schema.xml extract
> > ..
> > <field name="username" type="text_general" indexed="true" stored="true"
> />
> > <field name="name" type="text_general" indexed="true" stored="true"/>
> > <field name="autocomplete" type="textSpell" indexed="true" stored="false"
> > multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> > ...
> > <copyField source="username" dest="autocomplete"/>
> > <copyField source="name" dest="autocomplete"/>
> > ...
> >
> > <fieldType class="solr.TextField" name="textSpell"
> > positionIncrementGap="100">
> > <analyzer>
> > <tokenizer class="solr.StandardTokenizerFactory"/>
> > <filter class="solr.StandardFilterFactory"/>
> > <filter class="solr.LowerCaseFilterFactory"/>
> > </analyzer>
> > </fieldType>
> >
> >
> > solrconfig.xml
> >
> > ....
> > <lst name="spellchecker">
> > <str name="name">suggest</str>
> > <str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> > <str
> > name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> > <str name="field">autocomplete</str> <!-- the indexed field to derive
> > suggestions from -->
> > <float name="threshold">0.005</float>
> > <str name="buildOnCommit">true</str>
> > <!--
> > <str name="sourceLocation">american-english</str>
> > -->
> > </lst>
> >
> > </searchComponent>
> >
> > ..
> > <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> > name="/suggest">
> > <lst name="defaults">
> > <str name="spellcheck">true</str>
> > <str name="spellcheck.dictionary">suggest</str>
> > <str name="spellcheck.onlyMorePopular">true</str>
> > <str name="spellcheck.count">5</str>
> > <str name="spellcheck.collate">true</str>
> > </lst>
> > <arr name="components">
> > <str>spellcheck</str>
> > </arr>
> > </requestHandler>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by JMill <ap...@googlemail.com>.
I followed the instructions, I am able to browse to "
http://localhost:8983/solr/ac/browse?q=ce&debugQuery=true" but I am not
getting any suggestions (typed in c in Find Textbox).
I wonder if loading the example data is the problem? The response I get
after executing the script "feed-ac.sh" (step 3) is the following.
user$ ./feed-ac.sh
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int
name="QTime">2239</int></lst>
</response>
Are you able to confirm if this the expected response?
On Wed, Sep 25, 2013 at 1:46 PM, Ing. Jorge Luis Betancourt Gonzalez <
jlbetancourt@uci.cu> wrote:
> I've used a separated core for storing suggestions, based on what I see
> in: https://github.com/cominvent/autocomplete. You can check the blog
> post on
> www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/.
> This is really flexible, on the downside it does not use the suggester
> component su this are like regular queries against a separated core.
>
> Greetings!
>
> ----- Mensaje original -----
> De: "Erick Erickson" <er...@gmail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
> Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
>
> I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
> index (untokenized) something like
> Bill|Bill Rogers
> Rogers|Bill Rogers
>
> Your suggester then is a simple term lookup (see TermsComponent)
> which is quite fast. What you _don't_ get is autocorrect. But if you
> use terms.prefix, you can also control whether it's whole word match
> or not. To get whole-word in the above, you would set your prefix to
> "Rogers|" for instance. Or you may want to leave off the "|" to see
> more of an autocomplete-type response.
>
> Then, of course, when you display this you need to only display what's
> after the "|" (or whatever delimiter you use).
>
> One other note, this will be case sensitive, so you probably want to
> do casing yourself, index things like
> rogers|Bill Rogers
> and lowercase what you send in to terms component.
>
> Best,
> Erick
>
>
>
> On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com>
> wrote:
> > Hi,
> >
> > I'm using Solr's Suggester function to implement an autocomplete feature.
> > I have it setup to check against the "username" and "name" fields.
> Problem
> > is when running a query against the name, the second term, after
> > whitespace (surename) returns 0 results. Works if if query is a partial
> > name starting from the begining e.g. Given the name "Bill Rogers", a
> query
> > for Rogers will return 0 results whereas a query for "Bill" will return
> > positive (Bill Rogers). As for the username, it's not working at.
> >
> > I am after the following behaviour.
> >
> > Match any partial words in the fields "username" or "name" and return the
> > results. If there is match in the field "name" the return the whole name
> > e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> > single word that was a match)".
> >
> > schema.xml extract
> > ..
> > <field name="username" type="text_general" indexed="true" stored="true"
> />
> > <field name="name" type="text_general" indexed="true" stored="true"/>
> > <field name="autocomplete" type="textSpell" indexed="true" stored="false"
> > multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> > ...
> > <copyField source="username" dest="autocomplete"/>
> > <copyField source="name" dest="autocomplete"/>
> > ...
> >
> > <fieldType class="solr.TextField" name="textSpell"
> > positionIncrementGap="100">
> > <analyzer>
> > <tokenizer class="solr.StandardTokenizerFactory"/>
> > <filter class="solr.StandardFilterFactory"/>
> > <filter class="solr.LowerCaseFilterFactory"/>
> > </analyzer>
> > </fieldType>
> >
> >
> > solrconfig.xml
> >
> > ....
> > <lst name="spellchecker">
> > <str name="name">suggest</str>
> > <str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> > <str
> > name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> > <str name="field">autocomplete</str> <!-- the indexed field to derive
> > suggestions from -->
> > <float name="threshold">0.005</float>
> > <str name="buildOnCommit">true</str>
> > <!--
> > <str name="sourceLocation">american-english</str>
> > -->
> > </lst>
> >
> > </searchComponent>
> >
> > ..
> > <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> > name="/suggest">
> > <lst name="defaults">
> > <str name="spellcheck">true</str>
> > <str name="spellcheck.dictionary">suggest</str>
> > <str name="spellcheck.onlyMorePopular">true</str>
> > <str name="spellcheck.count">5</str>
> > <str name="spellcheck.collate">true</str>
> > </lst>
> > <arr name="components">
> > <str>spellcheck</str>
> > </arr>
> > </requestHandler>
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
> ________________________________________________________________________________________________
> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero
> del 2014. Ver www.uci.cu
>
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by "Ing. Jorge Luis Betancourt Gonzalez" <jl...@uci.cu>.
I've used a separated core for storing suggestions, based on what I see in: https://github.com/cominvent/autocomplete. You can check the blog post on www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/. This is really flexible, on the downside it does not use the suggester component su this are like regular queries against a separated core.
Greetings!
----- Mensaje original -----
De: "Erick Erickson" <er...@gmail.com>
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 6:16:51
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
index (untokenized) something like
Bill|Bill Rogers
Rogers|Bill Rogers
Your suggester then is a simple term lookup (see TermsComponent)
which is quite fast. What you _don't_ get is autocorrect. But if you
use terms.prefix, you can also control whether it's whole word match
or not. To get whole-word in the above, you would set your prefix to
"Rogers|" for instance. Or you may want to leave off the "|" to see
more of an autocomplete-type response.
Then, of course, when you display this you need to only display what's
after the "|" (or whatever delimiter you use).
One other note, this will be case sensitive, so you probably want to
do casing yourself, index things like
rogers|Bill Rogers
and lowercase what you send in to terms component.
Best,
Erick
On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com> wrote:
> Hi,
>
> I'm using Solr's Suggester function to implement an autocomplete feature.
> I have it setup to check against the "username" and "name" fields. Problem
> is when running a query against the name, the second term, after
> whitespace (surename) returns 0 results. Works if if query is a partial
> name starting from the begining e.g. Given the name "Bill Rogers", a query
> for Rogers will return 0 results whereas a query for "Bill" will return
> positive (Bill Rogers). As for the username, it's not working at.
>
> I am after the following behaviour.
>
> Match any partial words in the fields "username" or "name" and return the
> results. If there is match in the field "name" the return the whole name
> e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> single word that was a match)".
>
> schema.xml extract
> ..
> <field name="username" type="text_general" indexed="true" stored="true" />
> <field name="name" type="text_general" indexed="true" stored="true"/>
> <field name="autocomplete" type="textSpell" indexed="true" stored="false"
> multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> ...
> <copyField source="username" dest="autocomplete"/>
> <copyField source="name" dest="autocomplete"/>
> ...
>
> <fieldType class="solr.TextField" name="textSpell"
> positionIncrementGap="100">
> <analyzer>
> <tokenizer class="solr.StandardTokenizerFactory"/>
> <filter class="solr.StandardFilterFactory"/>
> <filter class="solr.LowerCaseFilterFactory"/>
> </analyzer>
> </fieldType>
>
>
> solrconfig.xml
>
> ....
> <lst name="spellchecker">
> <str name="name">suggest</str>
> <str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> <str
> name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> <str name="field">autocomplete</str> <!-- the indexed field to derive
> suggestions from -->
> <float name="threshold">0.005</float>
> <str name="buildOnCommit">true</str>
> <!--
> <str name="sourceLocation">american-english</str>
> -->
> </lst>
>
> </searchComponent>
>
> ..
> <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> name="/suggest">
> <lst name="defaults">
> <str name="spellcheck">true</str>
> <str name="spellcheck.dictionary">suggest</str>
> <str name="spellcheck.onlyMorePopular">true</str>
> <str name="spellcheck.count">5</str>
> <str name="spellcheck.collate">true</str>
> </lst>
> <arr name="components">
> <str>spellcheck</str>
> </arr>
> </requestHandler>
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
________________________________________________________________________________________________
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 2014. Ver www.uci.cu
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Posted by Erick Erickson <er...@gmail.com>.
I've sometimes seen this handled by clever tokenizing. For "Bill Rogers",
index (untokenized) something like
Bill|Bill Rogers
Rogers|Bill Rogers
Your suggester then is a simple term lookup (see TermsComponent)
which is quite fast. What you _don't_ get is autocorrect. But if you
use terms.prefix, you can also control whether it's whole word match
or not. To get whole-word in the above, you would set your prefix to
"Rogers|" for instance. Or you may want to leave off the "|" to see
more of an autocomplete-type response.
Then, of course, when you display this you need to only display what's
after the "|" (or whatever delimiter you use).
One other note, this will be case sensitive, so you probably want to
do casing yourself, index things like
rogers|Bill Rogers
and lowercase what you send in to terms component.
Best,
Erick
On Tue, Sep 24, 2013 at 2:01 PM, JMill <ap...@googlemail.com> wrote:
> Hi,
>
> I'm using Solr's Suggester function to implement an autocomplete feature.
> I have it setup to check against the "username" and "name" fields. Problem
> is when running a query against the name, the second term, after
> whitespace (surename) returns 0 results. Works if if query is a partial
> name starting from the begining e.g. Given the name "Bill Rogers", a query
> for Rogers will return 0 results whereas a query for "Bill" will return
> positive (Bill Rogers). As for the username, it's not working at.
>
> I am after the following behaviour.
>
> Match any partial words in the fields "username" or "name" and return the
> results. If there is match in the field "name" the return the whole name
> e.g. given the queries "Rogers" or "Bill"" return "Bill Rogers (not the
> single word that was a match)".
>
> schema.xml extract
> ..
> <field name="username" type="text_general" indexed="true" stored="true" />
> <field name="name" type="text_general" indexed="true" stored="true"/>
> <field name="autocomplete" type="textSpell" indexed="true" stored="false"
> multiValued="true" omitNorms="true" omitTermFreqAndPositions="false" />
> ...
> <copyField source="username" dest="autocomplete"/>
> <copyField source="name" dest="autocomplete"/>
> ...
>
> <fieldType class="solr.TextField" name="textSpell"
> positionIncrementGap="100">
> <analyzer>
> <tokenizer class="solr.StandardTokenizerFactory"/>
> <filter class="solr.StandardFilterFactory"/>
> <filter class="solr.LowerCaseFilterFactory"/>
> </analyzer>
> </fieldType>
>
>
> solrconfig.xml
>
> ....
> <lst name="spellchecker">
> <str name="name">suggest</str>
> <str name="classname">org.apache.solr.spelling.suggest.Suggester</str>
> <str
> name="lookupImpl">org.apache.solr.spelling.suggest.tst.TSTLookup</str>
> <str name="field">autocomplete</str> <!-- the indexed field to derive
> suggestions from -->
> <float name="threshold">0.005</float>
> <str name="buildOnCommit">true</str>
> <!--
> <str name="sourceLocation">american-english</str>
> -->
> </lst>
>
> </searchComponent>
>
> ..
> <requestHandler class="org.apache.solr.handler.component.SearchHandler"
> name="/suggest">
> <lst name="defaults">
> <str name="spellcheck">true</str>
> <str name="spellcheck.dictionary">suggest</str>
> <str name="spellcheck.onlyMorePopular">true</str>
> <str name="spellcheck.count">5</str>
> <str name="spellcheck.collate">true</str>
> </lst>
> <arr name="components">
> <str>spellcheck</str>
> </arr>
> </requestHandler>