[
https://issues.apache.org/jira/browse/OAK-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249918#comment-15249918
]
Marcel Reutegger commented on OAK-4233:
---------------------------------------
- The index would still be store in the repository, yes.
- The index editor would only have to update the index selected by the query
engine. Though, this would probably require more changes. Another optimization
is the path filter passed to the index. An index update may not be necessary
even if there are are pending changes, as long as those changes are not in the
subtree covered by the filter.
- Persisted index updates would still happen with the async index update as we
do right now.
- That's an implementation detail. In the most naive implementation each query
has it's own branch on top of the persisted base index. It may also be possible
to keep those in-memory branches for a short while (until the persisted index
is updated?) and share them when there are other concurrent queries.
> Property index stored locally
> -----------------------------
>
> Key: OAK-4233
> URL: https://issues.apache.org/jira/browse/OAK-4233
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk, query
> Reporter: Tomek Rękawek
> Priority: Minor
> Fix For: 1.6
>
>
> When running Oak in a cluster, each write operation is expensive. After
> performing some stress-tests with a geo-distributed Mongo cluster, we've
> found out that updating property indexes is a large part of the overall
> traffic. Let's try to create a new property-local index, that will save the
> indexed data locally, without sharing it.
> Assumptions:
> -there's a new {{property-local}} index type for which the data are saved in
> the local SegmentNodeStore instance created specifically for this purpose,
> -local changes are indexed using a new editor, based on the
> {{PropertyIndexEditor}},
> -remote changes are extracted from the JournalEntries fetched in the
> background read operation and indexed as well,
> -the new index type won't support uniqueness restriction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
