Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of arafalov@gmail.com designates
 209.85.218.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <1914812128.778592846.1426258454518.JavaMail.root@zimbra65-e11.priv.proxad.net>
References: 
 <CAEFAe-F0-R98siXgXsY9zUHCWTNPBvzbN9BVEkFBC92g+f2MNA@mail.gmail.com>
 <1914812128.778592846.1426258454518.JavaMail.root@zimbra65-e11.priv.proxad.net>
From: Alexandre Rafalovitch <arafalov@gmail.com>
Date: Fri, 13 Mar 2015 11:06:02 -0400
Message-ID: 
 <CAEFAe-H88j3wTiBR39Dmw6OyhWufGV7Ai6cvvhSYBVG-CVvPhg@mail.gmail.com>
Subject: Re: Word frequency
To: solr-user <solr-user@lucene.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The usual recommendation is to use Solr as a database, internally with
a separate user-facing app in a different container. Solr is not
really easy to secure, so best is to use O/S level protection, e.g.
listening on localhost only or only on a secure IP address.

This separate client also gives you more flexibility with scaling/etc later=
.

You could look at something like Spring Data Solr if your search needs
are simple and you want quick UI building support.

Regards,
   Alex.


----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/


On 13 March 2015 at 10:54,  <phiroc@free.fr> wrote:
>
> If you are asking whether users have access to /browse, then the answer i=
s yes.
>
> Currently, they can type keywords in the q input field to do searches.
>
> I plan to turn q into a hidden field and add a 'keywords' input field who=
se contents will be transferred to q when users press Search, using Javascr=
ipt.
>
> I will also add date selects so that users don't have to type date querie=
s.
>
> How do you secure the rest of SOLR (e.g., admin)?
>
> Would would recommend creating an alternative Search GUI with, say, Wicke=
t, which queries SOLR using AJAX?
>
> Sounds hard, but I will try. Velocity is so much simpler.
>
> Cheers,
>
> Philippe
>
>
>
>
>
>
>
> ----- Mail original -----
> De: "Alexandre Rafalovitch" <arafalov@gmail.com>
> =C3=80: "solr-user" <solr-user@lucene.apache.org>
> Envoy=C3=A9: Vendredi 13 Mars 2015 15:41:45
> Objet: Re: Word frequency
>
> On 13 March 2015 at 10:25,  <phiroc@free.fr> wrote:
>> I would like to:
>>
>> - loop throught the documents in my core
>> - extract the most-frequently-appearing words in each document's text fi=
eld
>> - generate a .vm  which displays those words ranked number of occurrence=
s, or, ideally, automatically generate that .vm whenever users use SOLR.
>
> That's what faceting does. You you can fine tune it further by telling
> how many of top hits you want to get back. Have a look at those
> parameters and play with them first in Web Admin UI before trying to
> apply them to the browse handler.
>
> Regards,
>    Alex.
> P.s. You are not planning to expose /browse handler directly to users,
> do you? Because unless you REALLY know how to secure the rest of Solr,
> you are asking for big troubles.