Return-Path: 
 <solr-user-return-91508-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org
Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D72B810165
	for <apmail-lucene-solr-user-archive@minotaur.apache.org>;
 Wed, 25 Sep 2013 18:00:10 +0000 (UTC)
Received: (qmail 81221 invoked by uid 500); 25 Sep 2013 18:00:00 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 80925 invoked by uid 500); 25 Sep 2013 18:00:00 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 80911 invoked by uid 99); 25 Sep 2013 17:59:59 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 17:59:59 +0000
X-ASF-Spam-Status: No, hits=1.8 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of apprentice321@googlemail.com
 designates 209.85.223.172 as permitted sender)
Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com)
 (209.85.223.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 17:59:53 +0000
Received: by mail-ie0-f172.google.com with SMTP id x13so14965ief.31
        for <solr-user@lucene.apache.org>;
 Wed, 25 Sep 2013 10:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=B/qzd/P0ITm10bvNEPV4FLfgaHxhGFYo6yaN3S4n354=;
        b=qyd5daikyUyYEQkRYrdH7V+TpgCqOswGHn7/tY2dr4hWS1RVP8mbPqaWQmj1u2VxRT
         ivXf0HBaPQMaYoGi3T67f92txnt++e4IVmX8NC5WfMCFK/WQLsBBBeogzm1XeT2KrNIl
         f770K2O5TGvlrNmc0fPjtC4OJtMs+WcBrUNDQxQQWI1KVbfnGxt3gQtohjTA7NGy5WEe
         /Z3Lgz4Ef+GoVHnWHaxM+p2zSGd0ByVHpwjJsu81//APXdbrUm5PM7C8uwazDR83A+Io
         NF4dwnuMJlLQJxWU0w7wqgf3no+ym3yAUbenXaqVekX+yf0/d46YwYTXEEaaIBvs0fjl
         LtKw==
MIME-Version: 1.0
X-Received: by 10.43.151.12 with SMTP id kq12mr17413045icc.55.1380131972352;
 Wed, 25 Sep 2013 10:59:32 -0700 (PDT)
Received: by 10.43.90.8 with HTTP; Wed, 25 Sep 2013 10:59:32 -0700 (PDT)
In-Reply-To: <5f98d232-1081-4efa-82a6-ef591ee0a83b@ucimail4.uci.cu>
References: 
 <CAHPiv5Ero2tE0y_nRqdXDK9g374s78Nqh81Nj6Rs+C4Qw=_H1w@mail.gmail.com>
	<5f98d232-1081-4efa-82a6-ef591ee0a83b@ucimail4.uci.cu>
Date: Wed, 25 Sep 2013 18:59:32 +0100
Message-ID: 
 <CAHPiv5HoJb3L_wK6ekyMqaGpo9pXG-m77yW62o9b7aT73=6Ovw@mail.gmail.com>
Subject: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
From: JMill <apprentice321@googlemail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2f8b8f4932f04e73903ce
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c2f8b8f4932f04e73903ce
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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=3D"text/javascript"
src=3D"#{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" <apprentice321@googlemail.com>
> Para: solr-user@lucene.apache.org
> Enviados: Mi=E9rcoles, 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 i=
n
>> 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>
>> Para: solr-user@lucene.apache.org
>> Enviados: Mi=E9rcoles, 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=3Dce&debugQuery=3Dtrue" 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=3D"1.0" encoding=3D"UTF-8"?>
>> <response>
>> <lst name=3D"responseHeader"><int name=3D"status">0</int><int
>> name=3D"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 se=
e
>> > 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" <erickerickson@gmail.com>
>> > Para: solr-user@lucene.apache.org
>> > Enviados: Mi=E9rcoles, 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 <

--001a11c2f8b8f4932f04e73903ce--