[
https://issues.jboss.org/browse/ISPN-4139?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-4139:
---------------------------------------
{quote}How is this even related?{quote}
Infinispan Query uses Hibernate Search, currently still using 4.5.0. So there are tests in
this tree which use Hibernate Search 4.5 in combination with the Lucene Directory too, run
with Lucene 3.6.2
We need to solve our integration issues in Hibernate Search to replace the one used by
Infinispan Query so that I can drop the need to have the Lucene Directory to support both
old and new Lucene versions. Current roadblock is the serialization, and as you know we
might introduce more roadbocks while making more changes in Search 5.. which is why
it's good to keep an eye on both projects as we need to converge quickly.
If you have a plan to fix this issue I'm happy to reassign to you as I've been
busy with debugging other Search issues, but be aware of the intricate compatibility
requirements. If you can avoid any SPI changes it would be best; otherwise I think
we'd be better off postponing this upgrade after we dropped Lucene 3.6, and postponed
the update in Search too.
Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
-----------------------------------------------------
Key: ISPN-4139
URL:
https://issues.jboss.org/browse/ISPN-4139
Project: Infinispan
Issue Type: Task
Components: Lucene Directory
Reporter: Hardy Ferentschik
Assignee: Sanne Grinovero
* {{DirectoryLuceneV4}} should not probably extend {{BaseDirectory}} instead of plain
{{Directory}}
* {{Lock#release}} got removed into {{Lock#close}}. {{BaseLuceneLock}} needs to change,
but I am not sure how this works in order to support Lucene 3 and 4!?
--
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