[
https://issues.apache.org/jira/browse/OAK-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771716#comment-13771716
]
Alex Parvulescu commented on OAK-1024:
--------------------------------------
The obvious fix is to add the '/' to the permitted characters. If that passes
the tests, I'll commit it.
> Full-text search on the traversing index fails if the condition contains a
> slash
> --------------------------------------------------------------------------------
>
> Key: OAK-1024
> URL: https://issues.apache.org/jira/browse/OAK-1024
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, query
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
>
> A full-text search on the traversing index falls back to a sort of manual
> evaluation of results.
> This is handled by the _FullTextTerm_ class, and it appears that it passes
> the constraint text through a cleanup process where it strips most of the
> characters that are neither _Character.isLetterOrDigit(c)_ not in the list
> _+-:&_
> I'm not exactly sure where this list comes from, but I see the '/' character
> is missing which causes a certain type of query to fail.
> Example:
> {code}
> //*[jcr:contains(., 'text/plain')]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
