[
https://issues.apache.org/jira/browse/OAK-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119403#comment-15119403
]
Andrei Dulvac edited comment on OAK-3694 at 1/27/16 3:10 PM:
-------------------------------------------------------------
In my opinion, this logic should be delegated to oak and provided to users, as
this logic could change at any time. Also, I think it's ok to rely on querying
to see if a node was indexed in the internal implementation, but does not seem
sensible to me to ask the client to do that.
was (Author: andrei.dulvac):
In my opinion, this logic should be delegated to oak and provided to users, as
this logic could change at any time. Also, I think it's ok to rely on querying
to see if a node was indexed, but does not seem sensible to me to ask the
client to do that.
> As a user, I want to know when a node that I've created has been indexed.
> -------------------------------------------------------------------------
>
> Key: OAK-3694
> URL: https://issues.apache.org/jira/browse/OAK-3694
> Project: Jackrabbit Oak
> Issue Type: Story
> Reporter: Valentin Olteanu
> Assignee: Chetan Mehrotra
> Fix For: 1.4
>
>
> As a user, I want to know when a node that I've created has been indexed so
> that I can start using it.
> Generalization: As a user, I want to know when everything created before
> timestamp T0 has been indexed.
> Ideal solution: MBean operation {{bool isIndexedBefore(long timestamp)}} that
> returns {{true}} if everything created before {{timestamp}} has been indexed
> (by all indexers).
> Current options:
> # check IndexStatsMBean for Start and Done to determine if a cycle has
> started after adding the node and has finished. Issue: there can be multiple
> async indexers. OAK-3606 proposes a solution.
> # add a node and search for it until it is retrieved. Issue: must add
> different nodes for different indexers and wait for all.
> These options are not precise (give false positives) and are not resilient to
> changes in indexing strategy (e.g. adding one more indexer breaks the
> checks).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
