[
https://issues.apache.org/jira/browse/SLING-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291146#comment-17291146
]
Stefan Seifert commented on SLING-10167:
----------------------------------------
i've provided a PR to fix the problem:
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/42
(i'm also wondering why all query in MapEntries.java use the deprecated SQL-1
JCR query syntax and not SQL-2, but this is a topic for another issue)
[~rombert] can you have a look - you where involved in SLING-9535
/cc [~akanksha88]
> MapEntries.loadAliases generets JCR queries with illegal absolute paths
> -----------------------------------------------------------------------
>
> Key: SLING-10167
> URL: https://issues.apache.org/jira/browse/SLING-10167
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.7.2
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Resource Resolver 1.7.4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> the code introduced with SLING-9535 generates JCR queries like this to load
> existing alias on startup:
> {noformat}
> SELECT sling:alias FROM nt:base AS page WHERE (NOT
> ISDESCENDANTNODE(page,"/jcr:system/")) AND sling:alias IS NOT NULL
> SELECT sling:alias FROM nt:base AS page WHERE (NOT
> ISDESCENDANTNODE(page,"/parent1/")) AND sling:alias IS NOT NULL
> {noformat}
> this query are invalid, as "/jcr:system/" or "/parent1/" are not valid paths
> - valid paths must end not with "/".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
