[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-233?pag...
]
sam doyle commented on HSEARCH-233:
-----------------------------------
So tracing through your code I do see that the my target collection and embedded for
@IndexedEmbedded are being picked up in your DocumentBuilder.initializeMember but at the
point where the processing is supposed to be done (I'm assuming looking at your code
and tracing) the BactchedQueueing.performWorks there is only one processor retrieved. The
workQueue that passed in has in its sealedQueue only work items related to my Zone
collection so the other collection is indeed missing from the indexing.
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