Uploaded image for project: 'Phoenix Tephra'
  1. Phoenix Tephra
  2. TEPHRA-240

TransactionConflictException should contain the conflicting key and client id

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.13.0-incubating
    • None
    • None

    Description

      Often transaction conflicts are hard to explain. Having the conflicting key, or even the name of the client that performed the concurrent update would greatly help debug.

      Attachments

        Issue Links

          links to

          Web Link GitHub Pull Request #47

          Activity

            People

              anew Andreas Neumann
              anew Andreas Neumann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: