jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (OAK-178) Query: index definition documentation and tooling
Date Thu, 04 Oct 2012 10:23:07 GMT

     [ https://issues.apache.org/jira/browse/OAK-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alex Parvulescu reassigned OAK-178:

    Assignee: Alex Parvulescu  (was: Thomas Mueller)
> 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: Alex Parvulescu
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message