[
https://hibernate.onjira.com/browse/HSEARCH-1034?page=com.atlassian.jira....
]
Sanne Grinovero updated HSEARCH-1034:
-------------------------------------
Description: The SearchMapping should not be discarded when SearchFactory instances
are rebuilt in background; mutations of the SearchFactory are triggered frequently by
Infinispan Query and this makes it impossible to use a programmatic SearchMapping: tests
seem to work at the first hit, but when new types are added they will be considered
unmapped, as the programmtic SearchMapping won't be available anymore. (was: The
ReflectionManager should not be discarded when SearchFactory instances are rebuilt in
background; mutations of the SearchFactory are triggered frequently by Infinispan Query
and this makes it impossible to use a programmatic SearchMapping: tests seem to work at
the first hit, but when new types are added they will be considered unmapped, as the
programmtic SearchMapping won't be available anymore.)
Pull Requests:
https://github.com/hibernate/hibernate-search/pull/225 (was:
https://github.com/hibernate/hibernate-search/pull/225)
Summary: Mutable SearchFactory should not drop programmatic SearchMapping (was:
Mutable SearchFactory should reuse the existing ReflectionManager)
Mutable SearchFactory should not drop programmatic SearchMapping
----------------------------------------------------------------
Key: HSEARCH-1034
URL:
https://hibernate.onjira.com/browse/HSEARCH-1034
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 4.1.0.Alpha1
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 4.1.0.Alpha2
The SearchMapping should not be discarded when SearchFactory instances are rebuilt in
background; mutations of the SearchFactory are triggered frequently by Infinispan Query
and this makes it impossible to use a programmatic SearchMapping: tests seem to work at
the first hit, but when new types are added they will be considered unmapped, as the
programmtic SearchMapping won't be available anymore.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira