[
https://issues.apache.org/jira/browse/OAK-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627549#comment-13627549
]
Jukka Zitting commented on OAK-763:
-----------------------------------
bq. observation scheduler
It would be better if each index component came with its own Runnable indexing
task and the only thing they'd share was the ScheduledExecutorService used to
trigger periodic indexing runs.
bq. index config deletes should remove listeners
I'd have one observer task per index component, so there's no need to add or
remove listeners for each individual index configuration.
bq. repo components setup gets difficult with this new scheduler in place
The ContentRepositoryImpl class should *not* need any knowledge of the
scheduler. Instead, the observation task of each index component should be
wired up directly with the underlying NodeStore and the execution scheduler.
bq. Assuming a full reindex can take quite some time for an already running
repository we could add a flag to the index config that would take that index
offline for the entire duration - which means it would be ignored by the query
engine.
Dunno. It sounds like a better approach would be to just leave the index as-is,
so concurrent queries can still leverage it and return at least some results
while reindexing is running. If an index is so badly out of date that it's
better to avoid using it during reindexing, the administrator can always remove
and recreate the index configuration to achieve the same effect.
> Asynchronous indexing
> ---------------------
>
> Key: OAK-763
> URL: https://issues.apache.org/jira/browse/OAK-763
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Attachments: OAK-763.patch
>
>
> It would be good to have the possibility to update indexes asynchronously,
> outside the current commit hook (or editor).
> This would be used for the index impls which can be a bit behind, like the
> ones that do text extraction from binaries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
