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

Thomas Mueller commented on OAK-178:
------------------------------------

I saw the following change is also needed:

#P oak-jcr
Index: 
src/main/java/org/apache/jackrabbit/oak/jcr/nodetype/NodeTypeManagerDelegate.java
===================================================================
--- 
src/main/java/org/apache/jackrabbit/oak/jcr/nodetype/NodeTypeManagerDelegate.java
   (revision 1360577)
+++ 
src/main/java/org/apache/jackrabbit/oak/jcr/nodetype/NodeTypeManagerDelegate.java
   (working copy)
@@ -47,6 +47,7 @@
         tmp.put("nt",  "http://www.jcp.org/jcr/nt/1.0";);
         tmp.put("mix", "http://www.jcp.org/jcr/mix/1.0";);
         tmp.put("xml", "http://www.w3.org/XML/1998/namespace";);
+        tmp.put("oak",  "http://jackrabbit.apache.org/oak/1.0";);
         nsdefaults = Collections.unmodifiableMap(tmp);
     }
 
With those two changes, the tests seem to work
                
> Query: index definition documentation and tooling
> -------------------------------------------------
>
>                 Key: OAK-178
>                 URL: https://issues.apache.org/jira/browse/OAK-178
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>
> Unlike Jackrabbit 2.x, indexes in the Oak query engine are user defined, that 
> means data is only indexed if there is a matching index. Those indexes are 
> then automatically used for the appropriate queries. The current plan is to 
> define indexes as nodes within a repository. An index is created if an index 
> metadata node is created, and the index is removed if the index metadata node 
> is removed. The index content is automatically updated if the content changes 
> (either synchronously or asynchronously).
> The location and structure of the index metadata needs to be defined and 
> documented.
> Also, to simplify defining and managing indexes, it may make sense to write a 
> utility (helper class) for managing indexes. Internally, this utility uses 
> the regular JCR API and accesses the documented index metadata nodes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to