I think you should extend the Directory class to provide a direct access
to the zip file in which the index is stored, and then use that
implementation with IndexWriter and IndexSearcher.
Waleed Tayea
-Original Message-
From: Ahmed El-
I need to access it as it is in the zip file. IndexSearcher cannot be
constructed using a zip file or a stream to a file. It can be
constructed to either FSDirectory or RAMDirectory. Both are not useful
in my case.
On 2/19/06, gekkokid <[EMAIL PROTECTED]> wrote:
> couldnt you use the java zip libr
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 toying with the
source. I am getting an error message I don't understand (though I
am admittedly new to ant). The error is
I've been trying to use ant to rebuild lucene after toying with the
source. I am getting an error message I don't understand (though I
am admittedly new to ant). The error is below. Any help is greatly
appreciated. Thank you.
Buildfile: build.xml
BUILD FAILED
/Users/michaeldodson/lucen
couldnt you use the java zip library
(http://java.sun.com/j2se/1.5.0/docs/api/java/util/zip/package-summary.html)
and compress and uncompress it separately? just an idea
- Original Message -
From: "Ahmed El-dawy" <[EMAIL PROTECTED]>
To:
Sent: Saturday, February 18, 2006 8:38 PM
Subjec
Hello,
Is there a way to access a Lucene Index which is stored inside a
.zip or .jar file?
This is important because my indexes are very large (> 200 M.B.) and I
need to compress them. I tried to store documents using
Store.COMPRESSED, but the compression ratio wasn't satisfying.
I need to add
I'm not sure you can do what you want in a single search. But, I'm not sure I
actually understand what your queries look like, either. I *think* you want
to search like
(title:a OR body:a) AND (title:b OR body:b) AND (title:c OR body:c)
not something like
(title:a OR title:b OR title:c) AND
I need to parse a query string, modify it a bit, and then output the
modified query string. This works quite well with query.toString(), except
that when I parse the query I set DEFAULT_OPERATOR_AND, and the output of
BooleanQuery.toString() assumes DEFAULT_OPERATOR_OR... Would be great if
this
Hi,
Well, I gave more thought to your suggestion and came
to the conclusion that I can not even run 2 searches.
The reason being, as I mentioned in my first message,
I am using MultiFieldQueryParser to search title and
body fields. Search terms can be found anywhere,
either in title or body or bot
SOME ONE wrote:
Yes, I could run two searches, but that means running
two searches for each request from user and that I
think doubles the job taking double time. Any
suggestions to do it more efficiently please ?
I think it would only take double time if the sets of hit documents have
substa
On Feb 18, 2006, at 6:11 AM, revati joshi wrote:
i'm facing problem while indexing the files .There r some
files which r not in normal ASCII format having ASCII characters
but r in some arabic,french format which i don't want to index
those files.
Because of these files my indexing
Hi,
i'm facing problem while indexing the files .There r some files which r
not in normal ASCII format having ASCII characters but r in some arabic,french
format which i don't want to index those files.
Because of these files my indexing process gets halted in between.so is there
any cl
Hi,
Yes, I could run two searches, but that means running
two searches for each request from user and that I
think doubles the job taking double time. Any
suggestions to do it more efficiently please ?
Thanks and Regards
Wiseman
--- "Michael D. Curtin" <[EMAIL PROTECTED]> wrote:
> SOME ONE wro
13 matches
Mail list logo
