We're updating the issue view to help you get more done. 

Using JMS with transactional backend should rollback even if master fails

Description

Currently it only works on JMS client side.

Shouldn't we make an option to make consumptions transactional as well? i.e. if the master takes a batch of Works A, then can not manage to flush that successfully to the IndexWriter, and fails, the next master node should still get A in his TODO list?

see https://github.com/hibernate/hibernate-search/pull/858

Environment

None

Status

Assignee

Unassigned

Reporter

Davide D'Alto

Labels

None

Suitable for new contributors

None

Pull Request

None

Feedback Requested

None

Components

Priority

Major