[ https://issues.apache.org/jira/browse/OAK-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379923#comment-14379923 ]
Chetan Mehrotra commented on OAK-2663: -------------------------------------- [~tmueller] [~mduerig] Can you review the patch. It would be helpful to have this included > Unique property index can trigger OOM during upgrade of large repository > ------------------------------------------------------------------------ > > Key: OAK-2663 > URL: https://issues.apache.org/jira/browse/OAK-2663 > Project: Jackrabbit Oak > Issue Type: Bug > Components: upgrade > Reporter: Chetan Mehrotra > Assignee: Chetan Mehrotra > Fix For: 1.1.8 > > Attachments: OAK-2663.patch > > > {{PropertyIndexEditor}} when configured for unique index maintains an in > memory state of indexed property in {{keysToCheckForUniqueness}}. This set > would accumulate all the unique values being indexed. > In case of upgrade where the complete upgrade is performed in single commit > this state can become very large. Further later while exiting the editor > validates that all such values are actually unique by iterating over all such > values. > We should look into other possible ways to enforce uniqueness constraint -- This message was sent by Atlassian JIRA (v6.3.4#6332)