Open JohnBDonner opened 9 years ago
Good idea
Might also need to set future for creating indexes in Elasticsearch since they could take a long time to complete before the hot-swap.
Where should the code that handles timeout configuration be placed?
I think if the results of LServing.serve(query: Q, predictions: Seq[P]): P
have to be wrapped into a Future[P]
, then the change needs to be made to both the projects.
On a broader scope, many of the calls in the project could have a Future
variant which support asynchronous calls.
LEventStore
has private val defaultTimeout = Duration(60, "seconds")
set as default, so first change should go in there ( PredictionIO ).
Why does LEventStore
have only blocking calls?
I'd like to request that request timeouts on predictions be configurable by the prediction query or the engine.json.
Such as in the
getBiasedRecentUserActions
method: