Uploaded image for project: 'Hibernate Search'
  1. HSEARCH-1921

Using JMS with transactional backend should rollback even if master fails

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: integration
    • Labels:
      None

      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

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                davided Davide D'Alto
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: