Hi Jeff and Doug,
I've just finished reading Chapter 1 of Lucene in Action (sample chapter
from Manning) and I've ordered a copy. The sample chapter was pretty
useful in giving me an idea of how Lucene will fit into my app and I
think it'll do the trick nicely with a bit of elbow grease on my part.
Thanks very much for the advice.
Cheers,
Kevin
Jeff Rodenburg wrote:
Kevin -
You've come to the right list to get information to help you make a
decision. That said, the responsible answer to your question will be
"it depends". The supporter in me says Lucene is your best choice,
hands down.
Your questions aren't as straightforward as you might expect. Lucene
is an API, not a full-fledged search engine. It's up to you to put it
to work within the confines of your operation, so determining what's
*best* can normally only be determined by yourself.
My suggestion to you: pick up a copy of Lucene in Action. You'll get
plenty of support on this mailing list, but you can educate yourself
much more effectively with that book. The authors lurk on this list.
It's the cheapest consulting ($40) you can get.
Cheers,
jeff
On 9/18/05, *Kevin Stembridge* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Would Lucene be a good choice for my app?
What is the best format to store documents in given that Lucene
needs to
search them but they still need to be rendered to a browser quickly?
How much development effort is usually involved in integrating Lucene
with an application?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
