On 03/02/2015 15:41, Michael Dürig wrote: > > Hi, > > I think we should keep this independent from indexing. Running the > counter consolidation asynchronously might have commonalities with > async indexing. If so, I'd first implement the former separately and > then factor out the commonalties. Discussed off-list with Michael came up with the proposed approach
- try out the index configuration approach as it should be a quick win. - refactor later on About the refactoring here's my thinking which I'd like to have some ideas as I didn't look at the details and something could be wrong. Right now we have a reliable way to run async processes (indexes in the specific case) in oak that is the async index. This has a known way of configuring the aspects by acting on oak:index/oak:queryIndexDefinition. Proposal: - rename the AsyncIndexUpdate into something like AsyncProcess - create a new area in the repo, beside the oak:index where we can configure these aspects. For example oak:processes/oak:processDefinition - instruct the AsyncProcess to understand this new area as well. Thoughts? D.
