Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-4232

GQL: Unexpected/strange behavior when searching for wildcards on property names

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Major
    • Resolution: Won't Do
    • 2.16.0
    • None
    • jackrabbit-core, query
    • AEM 6.2 SP1 CFP9
    • Important

    Description

      When using the Bulk Editor feature in AEM, the Jackrabbit GQL integration is actually consulted to execute the query.

      We were trying to search for nodes that have a property called 'name' that contains the letter 'a'.
      So, we were trying the following expression:

      name:a
      

      which was not working for some reason. So we figured it might have to do with wildcards, so we tried:

      name:*a*
      

      but that also did not work.

      Then we searched around and found the unit tests, which gave an indication of the bug that we encountered:
      https://searchcode.com/file/114218560/jackrabbit-core/src/test/java/org/apache/jackrabbit/core/integration/GQLTest.java

      In case you search for 'name', it does not actually use the property 'name', but instead the node name?

      And there does not seem to be a way to search for properties with wild cards; Any '*' seems to be ignored.

      Problems:

      • Not able to search for name-properties - Instead the node name is being searched (with full wildcard support)
      • Not able to search for any property with a wildcard - Instead the wildcards are dropped (ignored) (property:value* will become property:value)

      Attachments

        Activity

          People

            Unassigned Unassigned
            hkui Henry Kuijpers
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: