[siren-user] How reliant is SIREn on Lucene 3.x?

[Renaud Delbru]

Hi Rob,

On 16/08/11 13:10, Rob Vesse wrote:
> Hi All
>
> I've been talking recently to some of the Lucene.Net guys about working
> with them to help port SIREn to Lucene.Net but the problem we
> potentially have is that SIREn is built against Lucene 3.x which the
> Lucene.Net folks have not yet ported.
>
> So how reliant is SIREn on Lucene 3.x features, does it actually use any
> 3.x specific features or is it just built against it because its the
> latest version of Lucene?

The main changes in Lucene 3.0 was the new token stream api [1]. But 
this was introduced in Lucene 2.9. However, one class has been renamed 
(CharTermAttribute) differently in Lucene 3.0 which breaks compilation.
When I try to compile siren-core using lucene 2.9.4, I get errors like

java.lang.NoClassDefFoundError: 
org/apache/lucene/analysis/tokenattributes/CharTermAttribute

This is something to modify in order to make SIREn compatible with 
lucene 2.9.*. There are also all the Lucene Version flags (i.e., 
LUCENE_31) to change back to LUCENE_29.

The rest of siren-core and siren-parser should work. Concerning 
siren-solr, I don't exactly know what were the modifications, but I 
think they were minimal.

I hope this helps, let me know if you need more information. I could 
also provide you the source code of SIREn before the upgrade to Lucene 
3.0. This might helps you understanding what needs to be changed.

[1] http://www.slideshare.net/LucidImagination/whats-new-in-apache-lucene-30

Kind regards,
-- 
Renaud Delbru