You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/08/04 05:01:20 UTC

[jira] [Created] (OAK-4641) Using same index definition for both async and sync indexing

Chetan Mehrotra created OAK-4641:
------------------------------------

             Summary: Using same index definition for both async and sync indexing
                 Key: OAK-4641
                 URL: https://issues.apache.org/jira/browse/OAK-4641
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: query
            Reporter: Chetan Mehrotra
            Assignee: Chetan Mehrotra
             Fix For: 1.6


Currently one can set "async" flag on an index definition to indicate wether given index should be effective for synchronous commit or to be used for async indexing. For Hybrid Lucene indexing case OAk-4412 we need to have a way where same index definition gets used in both.

As discussed on DL [1] this can be done by

# Making {{async}} as a multi value property.
# Introducing a new IndexEditorProvider interface which can accept an IndexingContext instance. This provides access to 
## indexing mode - sync or async
## index path of the index (see OAK-4152)
## CommitInfo (see OAK-4640)

[1] http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201608.mbox/%3CCAHCW-mk1HzAxy8fk17SzYDcfLYY%3D0HUp93FCYoxpTP37cNgb%2Bg%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)