[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-233) EntityNotFoundException during indexing

[Hardy Ferentschik (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31654#action_31654 ] 

Hardy Ferentschik commented on HSEARCH-233:
-------------------------------------------

Can you be a little bit more specific?

> This was actually are result of the EntityNotFound exception kicking out of the main loop Hibernate Search uses that is responsible for indexing.
Any chance to get a full stack trace of this exception and where it occurred? When you say 'main loop' - what do you mean? You mentioned BatchedQueueingProcessor.processWorkByLayer  - is this what you mean?

> This situation can occur unfortunately with the data model I'm working with so my workaround solution was to trap the exception in the indexing loop and continue processing. I was then able to see most of the desired results. 
What do you mean you with "you caught the exception in the indexing loop". Are you saying you patched Hibernate Search or did you modify your custom indexing code?

> 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
>             Fix For: 3.1.0.CR1
>
>         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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira