[
https://issues.jboss.org/browse/ISPN-6252?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-6252:
---------------------------------------
What do you mean by "manipulate it" and/or change the slot? Can this be done at
runtime, on a per-deployment base?
We can not patch the static definition of existing modules, that would break other
applications.
An alternative: as far as I remember the only module which needs both worlds in the same
picture is the Infinispan DirectoryProvider for Hibernate Search: that's meant to link
to the Hibernate Search instance included in WildFly/EAP, and therefore should be using
its Lucene module (rather than the Infinispan/Lucene module).
Considering that Infinispan Query has its own very specific needs on how it sets up the
Directory, I'm wondering if we should rather not share the DirectoryProvider module
for both Query and Hibernate Search. If you make the Infinispan DirectoryProvider
compatible with Hibernate Search / WildFly only, and give Infinispan Query a similar
alternative we should be good and the two projects would be able to have completely
independent Lucene versions.
Upgrade to Apache Lucene 5.5
----------------------------
Key: ISPN-6252
URL:
https://issues.jboss.org/browse/ISPN-6252
Project: Infinispan
Issue Type: Component Upgrade
Components: Embedded Querying
Reporter: Sanne Grinovero
Assignee: Gustavo Fernandes
Fix For: 8.2.0.CR1
Apache Lucene 5.5 is released now, and is "drop-in compatible" with versions
5.3 and 5.4 so you don't have to wait for an Hibernate Search release.
It's also being the last one for the 5.x series before 6, so I expect that we'll
see some more micro releases for maintenance but essentially that this will be some form
of long term commitment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)