lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandre Rafalovitch <>
Subject Re: Word frequency
Date Fri, 13 Mar 2015 15:06:02 GMT
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.


Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:

On 13 March 2015 at 10:54,  <> wrote:
> If you are asking whether users have access to /browse, then the answer is 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 whose contents
will be transferred to q when users press Search, using Javascript.
> I will also add date selects so that users don't have to type date queries.
> How do you secure the rest of SOLR (e.g., admin)?
> Would would recommend creating an alternative Search GUI with, say, Wicket, which queries
SOLR using AJAX?
> Sounds hard, but I will try. Velocity is so much simpler.
> Cheers,
> Philippe
> ----- Mail original -----
> De: "Alexandre Rafalovitch" <>
> À: "solr-user" <>
> Envoyé: Vendredi 13 Mars 2015 15:41:45
> Objet: Re: Word frequency
> On 13 March 2015 at 10:25,  <> wrote:
>> I would like to:
>> - loop throught the documents in my core
>> - extract the most-frequently-appearing words in each document's text field
>> - generate a .vm  which displays those words ranked number of occurrences, 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.

View raw message