[
https://issues.apache.org/jira/browse/OAK-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu resolved OAK-500.
---------------------------------
Resolution: Duplicate
Assignee: Alex Parvulescu
duplicates OAK-511, which has been already fixed
> PropertyIndex: stored data in child nodes instead of properties
> ---------------------------------------------------------------
>
> Key: OAK-500
> URL: https://issues.apache.org/jira/browse/OAK-500
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Thomas Mueller
> Assignee: Alex Parvulescu
>
> Currently, the PropertyIndex (the one in package
> org.apache.jackrabbit.oak.plugins.index.property) stores index keys as
> properties in the same node. This is very good for cases where there are few
> entries in the index, but it problematic if there are many (because the node
> gets very big, and for conflict resolution handling).
> Instead of storing values in properties, index keys could be stored in child
> nodes. And index values (currently the list of paths) could be stored as
> properties (specially for unique indexes), or as child nodes (for index keys
> with many possible paths, for example a node type index, for node type
> "nt:unstructured"). This would result in possibly many nodes, but it would be
> relatively simple to implement (compared to a b-tree index).
--
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
