[hibernate-issues] [Hibernate-JIRA] Resolved: (HSEARCH-848) Isolated failures in backend work operations don't affect subsequent operations in same workQueue

[Sanne Grinovero (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanne Grinovero resolved HSEARCH-848.
-------------------------------------

    Resolution: Fixed

> Isolated failures in backend work operations don't affect subsequent operations in same workQueue
> -------------------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-848
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-848
>             Project: Hibernate Search
>          Issue Type: Improvement
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>             Fix For: 4.0.0.Alpha1
>
>
> With the new Hibernate Search backend, since we don't need to mandate order of LuceneWork operations, it's not needed to abort the full queue when a single operation fails.
> In practice since they are now applied in parallel, it's more effective and simpler to leave out this logic which was previously a requirement.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira