[jira] [Resolved] (OAK-517) Property2Index index content store strategy

["Alex Parvulescu (JIRA)" <ji...@apache.org>]

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

Alex Parvulescu resolved OAK-517.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6
         Assignee: Alex Parvulescu

all the pieces are in place, plus a hardcoded default impl to use as an example.

If we need another implementation, we'll also have to build a way to select it, probably based on node properties.
                
> Property2Index index content store strategy
> -------------------------------------------
>
>                 Key: OAK-517
>                 URL: https://issues.apache.org/jira/browse/OAK-517
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>             Fix For: 0.6
>
>         Attachments: OAK-517.patch
>
>
> Following OAK-511, I've realized that it should be simple enough to further refactor the code to provide a store(&retrieve) strategy.
> The strategy could be property based (PropertyIndex), based on paths of child nodes (Property2Index), or any kind of layered structured - possibly a btree like the old PropertyIndex had.
> This spans from the idea that the UUID index doesn't really need to have a new level of child nodes, it can easily keep the paths as properties.
> The up side is that we could play with the store strategy until we find one that fits each implementation we have, or even have a dynamic strategy that changes over time with the amount of content the index has to store.

--
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