(1) the manifest file may not be available (the class files may be
re-packaged in another app which didn't know to copy the Lucene
manifest stuff, or unpacked)
I'd like to hear others weigh in on this repackaging issue. Is this a
common practice?
There is one area where this is very common pract
I've got a handful of classes that I've written (and spoken about on
this list), and I occasionally get direct requests from people for that
code.
I figure it might be easier (for me) and more useful (for everyone else)
if this code was in the sandbox (or potentially in the main distribution).
The
Okay, hear me out for a sec:
This is *not* another "How can I update an existing Document in a Lucene
Index" question. I fully understand why "update" is not available, and
why update == delete + re-insert.
My request is not for a "update document" feature, but a "add to
document" feature.
Wh
how about http://dmoz.org/rdf
Perfect! And hierarchical data, as well!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
I'm doing a presentation to my local JUG on Lucene, and I'm looking for
a "good" set of documents to use as a demonstration.
Ideally it would be:
1) large (10,000 plus?).
2) contain some metadata besides "body" (like author, date, primarykey,
etc).
3) freely available.
I was going to u
red so that lexicographic sorting order is preserved.
*
*
* That is, if l1 is less than l2 for any two longs l1 and l2, then
* LongField.longToString(l1) is lexicographically less than
* LongField.longToString(l2). (Similarly for "greater than" and "equals".)
*
*
* This
