[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-233?pag...
]
sam doyle commented on HSEARCH-233:
-----------------------------------
After some debugging I have identified the problem.
As I mentioned in the original description:
"One side note that might be of interest is indexing of Zones results in referencing
some entities which don't exist that I'm catching due to the data not being in
sync."
Trapping this is not enough.
The BatchedQueueingProcessor.processWorkByLayer method invoked during the indexing process
was encountering this exception without trapping it. The resulting exception appears to
have caused the thread to die and the workQueue was not being updated with the required
data for the other collection.
I think it is common for an EntityNotFoundException to happen so this is something you
should probably look at.
S.D.
Only one @IndexedEmbedded collection working in my entity.
----------------------------------------------------------
Key: HSEARCH-233
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-233
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.0.1.GA
Environment: JBoss AS 4.2.2 Windows
Reporter: sam doyle
Attachments: jiraFiles.tar.gz, jiraFiles.tar.gz
This is supposedly pretty basic functionality so perhaps it is my particular case that it
is causing it.
In the attachment files the EmtVenue class is the root of the indexing.
It contains two @IndexedEmbedded
@OneToMany( cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy =
"emtVenue" )
@IndexedEmbedded
public Set<ClientGroupVenue> getClientGroupVenues()
@Embedded
@ManyToOne( fetch = FetchType.LAZY )
@JoinColumns( { @JoinColumn( nullable = false, name = "HOST",
referencedColumnName = "HOST" ),
@JoinColumn( nullable = false, name = "zone", referencedColumnName =
"ZONE" ) } )
@NotNull
@IndexedEmbedded
public Zones getZones()
In this case when I index EmtVenue the resulting index contains only values that
correspond to Zones and no ClientGroupVenues.
When I comment out the @IndexedEmbedded on the Zones the resulting index does show the
categories.
One side note that might be of interest is indexing of Zones results in referencing some
entities which don't exist that I'm catching due to the data not being in sync.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira