Try talking to these people:
http://www.google.com/search?ie=UTF-8&oe=UTF-8&q=jardirectory%20lucene
- Original Message
From: Ahmed El-dawy <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Saturday, February 18, 2006 3:38:16 PM
Subject: Accessing Lucene Index stored in a jar file
Thanks for your response.
You are both right.
As I didn't find an already made implementation for this, I am now
working in ZipDirectory class and I will send it to you as I finish
it.
Thanks alot
Ahmed Saad
On 2/19/06, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
> Try talking to these people:
>
I think it is not an easy task!!!
java.util.zip does not support random access to files inside an archive.
Lucene Directory requires files inside the directory to be accessed randomely.
Does anyone know a library to load archive files and gives a random
access to archived files?
On 2/19/06, Ahmed
Ant 1.6.5
No, I didn't make any modifications to the build file.
Mike
On Feb 19, 2006, at 1:09 AM, Erik Hatcher wrote:
What version of Ant? Did you modify build.xml?
Erik
On Feb 18, 2006, at 6:32 PM, Michael Dodson wrote:
I've been trying to use ant to rebuild lucene after toyi
While building a large index, we had a power outage. Over 2 million
documents had been added, each document with up to about 20 fields. The
size of the index on disk is ~500MB. When I started the process up again, I
noticed that documents that should have been in the index were missing. In
I don't know anything about it, but there's a library called TrueZip
(https://truezip.dev.java.net/) that apparently is "a drop-in
replacement for the File I/O classes in the J2SE API". Maybe it will
allow random access. I heard about on the Java Posse Pod Cast
(http://javaposse.com/)
Ahmed
markharw00d wrote:
Swing supports HTML and will do the highlight for you.
SwingText=""+highlighter.getBestFragment(tokenStream,text)+"";
If you don't like that approach and really do just want to just know the
positions, plug in your own "Formatter" class which, instead of marking
up the text,
On Feb 19, 2006, at 11:22 AM, Michael Dodson wrote:
Ant 1.6.5
No, I didn't make any modifications to the build file.
Something must be fishy with your Ant installation if you've not
modified build.xml or any build related files.
Is it possible you have another version of Ant mixed in to yo
Well, Ant 1.6.5 is the only one I've ever had. I just deleted the
whole thing and reloaded it without any luck.
The path looks like this:
/usr/local/ant/bin
"ant" above is a soft link to apache-ant-1.6.5 (set up as instructed
in the ant install docs).
Turns out this isn't a lucene isolat
Eight years after the invention of XML, DOM and SAX,
despite their respective issues, are still the mainstays
of application developers.
So is it the end of road for XML parsing innovation?
The VTD-XML project team think not. We are proud to
announce the availability of both C and Java ve
It is possible that your Documents were added to various index files, but those
were not yet "registered" in the "segments" file. Lucene knows only about
index segments that are listed in segments file. Any other files in the index
directories are ignored.
Also, some Documents are kept in mem
11 matches
Mail list logo