have to be ASL.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Manik Surtani <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Wednesday, January 30, 2008 8:38:48 AM
Subject: Re: JBoss Cache as a store
On
29
Jan
2008,
at
2
TED]>
To: java-dev@lucene.apache.org
Sent: Wednesday, January 30, 2008 8:38:48 AM
Subject: Re: JBoss Cache as a store
On
29
Jan
2008,
at
22:30,
Chris
Hostetter
wrote:
>
>
:
Is
there
a
set
of
tests
in
the
Lucene
sources
I
could
use
to
test
>
the
>
:
&quo
29 jan 2008 kl. 23.30 skrev Chris Hostetter:
I think most of the existing tests have the Directory impl hardcoded
in
them ... the best thing to do might be to refactor the existing
tests so
Directory creation comes from an overridable function in a subclass...
come ot think of it, Karl may
On 29 Jan 2008, at 22:30, Chris Hostetter wrote:
: Is there a set of tests in the Lucene sources I could use to test
the
: "JBCDirectory", as I call it? Perhaps something way I could
change the "index
: store provider" and re-run some existing tests, and perhaps add
some clustered
: te
: Is there a set of tests in the Lucene sources I could use to test the
: "JBCDirectory", as I call it? Perhaps something way I could change the "index
: store provider" and re-run some existing tests, and perhaps add some clustered
: tests specific to my plugin?
I think most of the existing tes
y, 29 January, 2008 3:38:17 PM
Subject: Re: JBoss Cache as a store
Bump.
Anyone?
On
24
Jan
2008,
at
14:07,
Manik
Surtani
wrote:
>
Hi
guys
>
>
I've
just
written
a
plugin
for
Lucene
to
use
JBoss
Cache
as
an
index
>
store.
The
benefits
of
something
Bump. Anyone?
On 24 Jan 2008, at 14:07, Manik Surtani wrote:
Hi guys
I've just written a plugin for Lucene to use JBoss Cache as an index
store. The benefits of something like this are:
1. Faster access to indexes as they will be in memory
2. Indexes replicated across a cluster of ser
Hi guys
I've just written a plugin for Lucene to use JBoss Cache as an index
store. The benefits of something like this are:
1. Faster access to indexes as they will be in memory
2. Indexes replicated across a cluster of servers
3. Indexes "persisted" in clustered memory - faster that per
