[hibernate-dev] Hibernate Search being integrated in WildFly

[Sanne Grinovero]

On 14 January 2014 15:46, Scott Marlow <smarlow at redhat.com> wrote:
> I am a big fan of Hibernate technologies and the search capabilities.  I am
> concerned though that we are deferring how to untangle the Hibernate
> Search/Infinispan/WildFly dependencies.
>
> I raised a few questions on the wildfly-dev mailing list, some that got
> answered but one important issue didn't.  The question is about scheduling
> and how to coordinate the WildFly/Hibernate ORM/Hibernate Search/Infinispan
> releases such that if one component breaks the others at the end of a
> release cycle, how to deal with that.  This isn't really my problem as I
> don't schedule any of these components but it would be wrong of me not to
> point this out.

We'll try to coordinate version compatibility across projects; We do
control the version being used in Infinispan and will keep it up to
date as there are various good reasons to do that.
The tricky part is that we don't control necessarily which versions of
ORM and Infinispan are going to be picked in a specific WildFly
release, but optimistically speaking I expect that this choice will
always be at "same generation".

To address the more pessimistic scenario, we'll need to be more
flexible in having +1 / -1 version compatibility at SPI levels.
Historically we'll have been quite good at keeping a level of
flexibility, but you're right it is a concern and we'll be handling
stricter compatibility checks via new CI jobs.
Worst case, we'll always be able to deploy additional modules.

>
> Are there any infinispan-dev mailing list threads discussing how to remove
> the Infinispan dependency on Hibernate Search in 2014, so that we aren't
> forced into keeping Hibernate Search in WildFly 9?

Not yet, if any now that it's being included I think it should stay
there. A major release is a big change for our point of view but not a
reason to completely disrupt users's experience, from their point of
view it's not nice that the way to deploy something like this changes
*that* frequently.

>
>
> On 01/13/2014 06:06 PM, Sanne Grinovero wrote:
>>
>> Hello,
>> as you might already know by following the WildFly developer's mailing
>> list, most of the Hibernate Search jars and dependencies (Lucene) are
>> now included in the application server as modules.
>>
>> This was not primarily driven by practical need of Hibernate users but
>> rather because of clustering needs of the application server, and also
>> CapeDwarf and other projects make extensive use of it.
>>
>> Just a couple of small adjustments are needed to make it possible for
>> Hibernate users to also take advantage of it, so I'd think we should
>> make these adjustments to make it more useful?
>>
>> This is what I'm thinking:
>>   - The hibernate-search-orm jar is missing (an essential jar for our
>> purposes)
>>     -> add a module
>>   - No additional analyzers are included
>>     -> see how optional modules work, so that - while we won't ship all
>> those dependencies - it's still easy to add when you need one
>>   - Jipijapa should help?
>
>
> Jipijapa could help standardize how WildFly integrates with search
> providers.  I'm not sure if this is needed.

I mean, I think it's probably Jipijapa's responsibility to inject the
module on the classpath for Hibernate users.

>
>
>>     -> should we make Hibernate Search available to deployments
>> whenever Hibernate ORM is made available?
>
>
> Would this slow deployment down at all for applications that don't use
> Hibernate Search?

No, not at all.

Sanne

>>   - Get it to a reasonable version: it's including 4.5.0.Alpha2 now
>>     -> we need to release a Beta soon, any volunteer? I'm stuck on an
>> island with extremely slow connectivity.
>>   - Contribute some integration tests to WildFly: there aren't any
>> today verifying the included modules
>>
>> What shall we do about our modules distribution? I think it would be
>> nice to continue maintaining that, so that we can make frequent
>> releases and that would allow users to use a different version than
>> what they would get in WildFly - if they want to.
>>
>> -- Sanne
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>