terms of an application, not
an engine. Lucene is what you build your application around, it provides the
guts of the searching. The rest is up to your.
HTH
Erick
Cheers,
>
> w
>
>
> -Original Message-
> From: Lance Norskog [mailto:goks...@gmail.com]
> Sent: Donnerst
Cheers,
w
-Original Message-
From: Lance Norskog [mailto:goks...@gmail.com]
Sent: Donnerstag, 26. August 2010 05:25
To: java-user@lucene.apache.org
Subject: Re: Lucene applicability
A stepping stone to the above is that, in DB terms, a Lucene index is
only one table. It has a suite of indexing fea
A stepping stone to the above is that, in DB terms, a Lucene index is
only one table. It has a suite of indexing features that are very
different from database search. The features are oriented to searching
large bodies of text for "ideas" rather than concrete words. It
searches a lot faster than a
The SOLR wiki has lots of good information, start there:
http://wiki.apache.org/solr/
Otherwise, see below...
On Wed, Aug 25, 2010 at 6:20 AM, Schreiner Wolfgang <
wolfgang.schrei...@itsv.at> wrote:
> Hi all,
>
> We are currently evaluating potential search frameworks (such as Hibernate
> Search
I see you are coming from the database world. To get a better understanding
of Lucene, I would suggest you use the free version of DBSight, which let
you create Lucene index with SQL after a few clicks.
Basically Lucene is more like a list of denormalized documents. So if you
change your database
Hi all,
We are currently evaluating potential search frameworks (such as Hibernate
Search) which might be suitable to use in our project (using Spring, JPA with
Hibernate) ...
I am sending this E-Mail in hope you can advise me on a few issues that would
help us in our decision making process.
