[
https://issues.apache.org/jira/browse/OAK-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667092#comment-15667092
]
Manfred Baedke commented on OAK-3606:
-------------------------------------
[~chetanm],
I'm unsure if there is still a bug or if I don't get the architecture. With the
current trunk I'd expect the CommitInfo created in
AsynIndexUpdate.mergeWithConcurrencyCheck() to show up in the IndexingContext
used in LucenIndexEditorProvider.getIndexEditor(). Wrong?
> Improvements for IndexStatsMBean usage
> --------------------------------------
>
> Key: OAK-3606
> URL: https://issues.apache.org/jira/browse/OAK-3606
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, lucene
> Affects Versions: 1.3.9
> Reporter: Thierry Ygé
> Assignee: Manfred Baedke
> Fix For: 1.6, 1.5.14
>
> Attachments: adding_new_MBean.patch,
> new_mbean_interface_and_implementation.patch
>
>
> When running integration tests, it is common to have the need to wait for the
> async indexes to have been executed. So that the test can successfully
> validate operations that depend on the search result.
> With the current IndexStatsMBean implementation it cannot return the start
> time of the last successful indexing. It provide a "LastIndexedTime" which is
> not sufficient to know if changes made recently are now indexed.
> The idea is to set the start time as value of a new attribute (i.e
> "StartLastSuccessIndexedTime") to the IndexStatsMBean.
> Then create a new Mbean that calculate from all existing IndexStatsMBean (as
> multiple are possible now) the oldest "StartLastSuccessIndexedTime".
> That will allow integration tests to be able to wait until that oldest
> "StartLastSuccessIndexedTime" is greater than the time it started to wait.
> Attached is a sample patch containing the necessary changes (for a Oak core
> 1.4.0-SNAPSHOT).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
