Jackrabbit Oak
  1. Jackrabbit Oak
  2. OAK-583

Inconsistencies in property index definitions

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None

      Description

      while trying to simplify the property-index definitions and adding
      one for the access control content, i detected the following inconsistencies
      with the property "propertyNames":

      • the property is sometimes single valued (e.g. "uuid") and sometimes
        multivalued ("nodetypes")
        IMO the property name implies that it is multivalued. however, i get the
        impression that this doesn't work for unique property index definitions.
        (test failure)
      • the property is defined using Type.STRING (implicit) or Type.STRINGS.
        IMO however, Type.NAMES would be more appropriate.
      • while moving out the user related index, i used type name without noticing.
        i will change to STRING(S) such that we have it consistent (see above).

        Activity

          People

          • Assignee:
            Alex Parvulescu
            Reporter:
            angela
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development