[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-233?pag...
]
sam doyle commented on HSEARCH-233:
-----------------------------------
No I am not using hibernate.search.worker.execution=async. My solution was to simply wrap
the loop within
private void processWorkByLayer(List<Work> queue, int initialSize,
List<LuceneWork> luceneQueue, Layer layer)
with a try catch block so that it continue. I tried @NotFound( action =
NotFoundAction.IGNORE) but it did not seem to work. Besides, I would hope the application
would be able report the issue and continue without completely coming to a halt.
EntityNotFoundException during indexing
---------------------------------------
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
Assignee: Hardy Ferentschik
Fix For: 3.1.0.GA
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