[
https://issues.apache.org/jira/browse/OAK-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460576#comment-16460576
]
Chetan Mehrotra commented on OAK-4638:
--------------------------------------
[~tmueller] [~catholicon] Should we resolve this issue as OAK-6535 implemented
the approach discussed here. Whats left is work on converting existing indexes
to switch to Lucene based indexes which can be done in a separate issue
dedicated for the conversion.
Currently this issue being open conveys that indexing support needs to be
implemented which is misleading
> Mostly async unique index (for UUIDs for example)
> -------------------------------------------------
>
> Key: OAK-4638
> URL: https://issues.apache.org/jira/browse/OAK-4638
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: property-index, query
> Reporter: Thomas Mueller
> Priority: Major
>
> The UUID index takes a lot of space. For the UUID index, we should consider
> using mainly an async index. This is possible because there are two types of
> UUIDs: those generated in Oak, which are sure to be unique (no need to
> check), and those set in the application code, for example by importing
> packages. For older nodes, an async index is sufficient, and a synchronous
> index is only (temporarily) needed for imported nodes. For UUIDs, we could
> also change the generation algorithm if needed.
> It might be possible to use a similar pattern for regular unique indexes as
> well: only keep the added entries of the last 24 hours (for example) in a
> property index, and then move entries to an async index which needs less
> space. That would slow down adding entries, as two indexes need to be checked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
