[
https://issues.apache.org/jira/browse/SOLR-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134597#comment-15134597
]
Varun Thacker commented on SOLR-8534:
-------------------------------------
I don't think so. REQUESTSTATUS_OP returns a null and the check is -
{code}
Map<String, Object> props = operation.call(req, rsp, this);
String asyncId = req.getParams().get(ASYNC);
if (props != null) {
if (asyncId != null) {
props.put(ASYNC, asyncId);
}
{code}
Which means all calls which are currently being handled by the collections
handler directly will return null and the async param won't get applied
As a future enhancement we need to allow async calls to actions handled by the
collections handler as well
> Add generic support for Collection APIs to be async
> ---------------------------------------------------
>
> Key: SOLR-8534
> URL: https://issues.apache.org/jira/browse/SOLR-8534
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Fix For: 5.5, Trunk
>
> Attachments: SOLR-8534.patch, SOLR-8534.patch, SOLR-8534.patch,
> SOLR-8534.patch
>
>
> Currently only a handful of Collection API calls support the async parameter.
> I propose to extended support for async to most APIs.
> The Overseer has a generic support for calls to be async. So we should
> leverage that and make all commands implemented within the
> OverseerCollectionMessageHandler to support async
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
