Lucene JCR Index

[Nicolas Belisle <Ni...@bibl.ulaval.ca>]

Hi,

I've contributed a JCR Directory implementation for Lucene.

What it does: allows the storage of indexes in a JCR repository
Why: single place for content and index storage, transaction support (if 
the JCR implementation support them),
Performance: JCR does not support random access (only plain Inputstreams), 
but my implementation splits the files into fixed-size buffers to help 
performance. It will also depend on the persistence mechanism used with JCR.
Status: beta

You can retrieve the code there:
http://issues.apache.org/jira/browse/LUCENE-484

I welcome your comments.

Regards,


Nicolas Bélisle

Laval University Library

Re: Lucene JCR Index

[Marcel Reutegger <ma...@gmx.net>]

Hi Nicolas,

very interesting idea. I'll look into it as soon as possible.

that would allow us to commit index changes together with regular 
content changes in the same jcr transaction.

regards
  marcel

Nicolas Belisle wrote:
> Hi,
> 
> I've contributed a JCR Directory implementation for Lucene.
> 
> What it does: allows the storage of indexes in a JCR repository
> Why: single place for content and index storage, transaction support (if 
> the JCR implementation support them),
> Performance: JCR does not support random access (only plain 
> Inputstreams), but my implementation splits the files into fixed-size 
> buffers to help performance. It will also depend on the persistence 
> mechanism used with JCR.
> Status: beta
> 
> You can retrieve the code there:
> http://issues.apache.org/jira/browse/LUCENE-484
> 
> I welcome your comments.
> 
> Regards,
> 
> 
> Nicolas Bélisle
> 
> Laval University Library
> 
> 
> 
> 
> 
> 
> 
> 
> 

Re: Lucene JCR Index

[Nicolas Belisle <Ni...@bibl.ulaval.ca>]

Hi,

Sorry for my late response.

I took a quick look at Compass documentation.
I think one has to subclass 
org.compassframework.core.lucene.engine.store.AbstractLuceneSearchEngineStore 
if he wishes to add a custom storage mechanism.
They use a connection parameter for configuration. 
LuceneSearchEngineStoreFactory seems to create the appropriate 
AbstractLuceneSearchEngineStore implementation based on the connection 
prefix. One could add, for example, a jcr: prefix that looks in JNDI for a 
repository.
 From there, one should be able to use Compass as with other storage 
mechanisms.
I do not know for transactions support. I think can they retrieve JTA 
transaction from JNDI. I suppose the storage implementation is responsible 
for publishing it ?

Regards,

Nicolas


Le 20:25 2006-01-12, vous avez écrit:
>Hi
>
>must be "lucene-day" today
>see also:
>http://www.theserverside.com/news/thread.tss?thread_id=38478
>their main feature:
>"Being able to store the Lucene indexes in a database [...]"
>haven't had a deeper look at yours but maybe your project can align nicely 
>with compass.
>I like compass because it works nicely with spring, so a JCR+Lucene+Spring 
>stack would be good.
>
>If it doesn't fit in your strategy just ignore it as a random wild thought.
>
>kind regards
>Philipp
>
>Nicolas Belisle wrote:
>
>>Hi,
>>
>>I've contributed a JCR Directory implementation for Lucene.
>>
>>What it does: allows the storage of indexes in a JCR repository
>

Re: Lucene JCR Index

[Philipp Jurewicz <Ph...@gmx.net>]

Hi

must be "lucene-day" today
see also:
http://www.theserverside.com/news/thread.tss?thread_id=38478
their main feature:
"Being able to store the Lucene indexes in a database [...]"
haven't had a deeper look at yours but maybe your project can align 
nicely with compass.
I like compass because it works nicely with spring, so a 
JCR+Lucene+Spring stack would be good.

If it doesn't fit in your strategy just ignore it as a random wild thought.

kind regards
Philipp

Nicolas Belisle wrote:

> Hi,
>
> I've contributed a JCR Directory implementation for Lucene.
>
> What it does: allows the storage of indexes in a JCR repository