[
https://issues.apache.org/jira/browse/JCR-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150505#comment-13150505
]
Marcel Reutegger commented on JCR-3147:
---------------------------------------
> can (and should) also be used for immediate execution of parallel tasks
I agree that it should but currently it can't, because all tasks are treated
equally.
I think an important feature that is missing currently, is the ability to
specify a 'queue policy'. A client should be able to specify if it is OK to
queue the task and execute it later when all the threads in the pool are busy.
This would be similar to the RejectedExecutionHandler but would already kick in
when the the pool is busy.
> AbstractIndex should use the repository executor for indexing tasks
> -------------------------------------------------------------------
>
> Key: JCR-3147
> URL: https://issues.apache.org/jira/browse/JCR-3147
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Alex Parvulescu
> Priority: Minor
> Attachments: JCR-3147.patch
>
>
> The AbstractIndex still uses its own executor for indexing tasks, it should
> switch to the global repository executor.
> It should also mark the tasks as 'low priotiry' as soon as JCR-3146 gets into
> the trunk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
