jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-5707) [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, analyzed
Date Wed, 08 Mar 2017 11:20:38 GMT

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

Vikas Saurabh updated OAK-5707:
    Attachment: OAK-5707-v2-WIP.patch

Adding [^OAK-5707-v2-WIP.patch] as bit better (yet completely unfit-to-commit) WIP version.

> [Oak lucene indexes] Clarify aggregates, nodeScopeIndex, propertyIndex, analyzed
> --------------------------------------------------------------------------------
>                 Key: OAK-5707
>                 URL: https://issues.apache.org/jira/browse/OAK-5707
>             Project: Jackrabbit Oak
>          Issue Type: Documentation
>            Reporter: David Gonzalez
>            Assignee: Vikas Saurabh
>         Attachments: OAK-5707.patch, OAK-5707-v2-WIP.patch
> Oak lucene documentation would benefit from clarifying the relationships and expect behaviors
around aggregates, nodeScopeIndex, propertyIndex and analyzed.
> These features have some overlap in what they do and/or augment one another, but to the
lay-developer it is unclear how these work in concern and/or the implications of these using
the various features.
> Its worth remembering many developers are under the mindset (shifting from jackrabbit
2 -> oak) that oak indexing requires explicit inclusion of content into search results;
thus implicit content inclusion into indexes via generalized aggregations (vs named properties)
is unclear/unexpected to many.

This message was sent by Atlassian JIRA

View raw message