Henry Kuijpers created JCR-4232:
-----------------------------------
Summary: GQL: Unexpected/strange behavior when searching for
wildcards on property names
Key: JCR-4232
URL: https://issues.apache.org/jira/browse/JCR-4232
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core, query
Affects Versions: 2.16.0
Environment: AEM 6.2 SP1 CFP9
Reporter: Henry Kuijpers
Priority: Critical
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:
{code:gql}
name:a
{code}
which was not working for some reason. So we figured it might have to do with
wildcards, so we tried:
{code:gql}
name:*a*
{code}
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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
