[
https://issues.apache.org/jira/browse/SOLR-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200482#comment-15200482
]
Alan Woodward commented on SOLR-8782:
-------------------------------------
Yes, it's a bit of a pain. It's because the return type of all the .setAsyncId
methods are different. In trunk, once .setAsyncId is removed and all async
calls are made via processAndWait(), we can move the identical methods into the
Async base class. For now they're left as abstract to ensure that they get
implemented properly.
> Improve SolrJ Collections async API
> -----------------------------------
>
> Key: SOLR-8782
> URL: https://issues.apache.org/jira/browse/SOLR-8782
> Project: Solr
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Fix For: 6.1
>
> Attachments: SOLR-8782.patch, SOLR-8782.patch
>
>
> The async collections API is a bit difficult to use at the moment:
> - you need to create your own async ID and add it to the request
> - you then need to create a different request and poll to find out when you
> get a response
> - the implementation requires some complex generics just to allow a chained
> .setAsync() method
> I think we can improve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
