[ 
https://issues.apache.org/jira/browse/OAK-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882878#comment-13882878
 ] 

Alex Parvulescu commented on OAK-1354:
--------------------------------------

bq. getColumnSelectorNames() method used by getNodes() seems to return an empty 
set of names

It looks like this comes from the fact that registering a custom mixin will 
leave the 'rep:namedSingleValuedProperties' empty [0]
I'm now trying to inject the selector name to see if it will work.

[0] 
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/query/ast/SelectorImpl.java#L172

> Valid Query for mixin Type in JCR 2.x fails in Oak
> --------------------------------------------------
>
>                 Key: OAK-1354
>                 URL: https://issues.apache.org/jira/browse/OAK-1354
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 0.11
>            Reporter: Dominik Süß
>            Assignee: Alex Parvulescu
>
> In a Sling based environment running on Oak 0.12.0.r1548152b I'm facing an 
> issue resulting in a 500 error in Sling due to a repository exception when 
> executing the following query through the Sling Resource Resolve 
> that did work in the equivalent JCR 2 based environment.
> {code}
> resolver.findResources("SELECT * FROM [my:custommixin]", Query.JCR_SQL2)
> {code}
> The custom mixing was added to the reqo via vlt package (mvn-vlt plugin by 
> Adobe) and results (as well as the corresponding XPATH version in the 
> following stackstrace:
> {code}javax.jcr.RepositoryException: Query contains more than one selector: []
>       at 
> org.apache.jackrabbit.oak.jcr.query.QueryResultImpl.getNodes(QueryResultImpl.java:163)
>       at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.findResources(JcrResourceProvider.java:261)
> {code}
> The further stacktrace seems irrelevant, but I can provide more if required.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to