Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-5173

Path in uniqueness constraint violation exception is always the root

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.10, 1.5.14
    • Fix Version/s: 1.7.12, 1.8.0
    • Component/s: core, property-index
    • Labels:
      None

      Description

      OAK-1997 added a (single) path to the uniqueness constraint exception message in the PropertyIndexEditor to point out where the duplicate came from, but it is always the root:

      OakConstraint0030: Uniqueness constraint violated at path [/] for one of the property in [rep:externalId] having value xyz1234
      

      That is because it uses getPath() of the index editor itself and the uniqueness check always happens at the root level at the end.

      It probably has to read from the index to find out the 2 or more paths with the same property value (just printing one path is not enough information for duplicates).

        Attachments

          Activity

            People

            • Assignee:
              thomasm Thomas Mueller
              Reporter:
              alexander.klimetschek Alexander Klimetschek
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: