[infinispan-issues] [JBoss JIRA] (ISPN-2689) Support storage of indexes of Apache Lucene 4

[James Aley (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744031#comment-12744031 ] 

James Aley edited comment on ISPN-2689 at 1/8/13 7:24 AM:
----------------------------------------------------------

I've attached a very hacky proof of concept. I basically just forked the module and patched the code to build with Lucene 4, then everything magically worked!

So it seems some very trivial changes can in fact make what we have now at least work with Lucene 4.0 - though not in a backwards compatible way.

Question now is, what's the best way to make both a Lucene 3 and 4 compatible version (or versions) available to users?
                
      was (Author: jaley):
    I've attached a very hacky proof of concept. I basically just forked the module and patched the code to build with Lucene 4, then everything magically worked!

So it seems some very trivial changes can in fact make what we have now at least work with Lucene 4.0 - though not in a backwards compatible way.

Question now is, what's the best way to make both a Lucene 3 and 4 compatible version (or version) available to users?
                  
> Support storage of indexes of Apache Lucene 4
> ---------------------------------------------
>
>                 Key: ISPN-2689
>                 URL: https://issues.jboss.org/browse/ISPN-2689
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Lucene Directory
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>             Fix For: 6.0.0.Beta1, 6.0.0.Final
>
>         Attachments: ISPN-2689-hack-main.diff, ISPN-2689-hack-test.diff
>
>
> The current Lucene Directory supports Lucene version from 2.9 to 3.6,
> but Lucene 4 made consistent changes which might need a new module.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira