Hibernate Search is currently requiring to be able to re-read the
metada for on-the-fly reconfiguration of the mapped entities, but if
we can reload the Jandex index every time that's needed that would be
fine. This "internal reboot" is slow anyways and not expected to
In short: it's ok to release references to the index, but needs a way
to reload it if needed.
On 28 June 2012 15:07, Scott Marlow <smarlow(a)redhat.com> wrote:
On 06/26/2012 12:29 PM, Hardy Ferentschik wrote:
> On Jun 26, 2012, at 6:19 PM, Sanne Grinovero wrote:
>> an optimization we have been discussing but had still no time to
>> implement is to update hibernate-commons-annotations to use Jandex.
> +1 for Jandex. However, I don't think it is worth to trying to use it with
> the old configuration code.
> The new metamodel will use jandex and I rather see that we get this work
> complete instead of
> making major changes to the existing annotation processing. That's kind of
> doing twice the work.
> -1 for updating hibernate-commons-annotations. I think we should get rid
> of it.
We should ensure that the Jandex instance is not referenced after deployment
is complete (otherwise we will keep the large Jandex in memory but not use
it any more).
If there are non-deployment (time) tasks that we want to use the Jandex for,
we would probably need Jandex changes to accommodate that.