[OAK-583] Inconsistencies in property index definitions

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: core
• Assignee: Alex Deparvu
• Reporter: Angela Schreiber
• Created: 24/Jan/13 11:07
• Updated: 06/May/13 15:55
• Resolved: 01/Mar/13 15:22

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).