Add selected engine name to QueryAPI.update_cache
arguments
#1016
Labels
category: feature
New feature or request
QueryAPI.update_cache
arguments
#1016
Overview
It sometimes might be helpful for profiling purposes for a service using an external plugin to have access to what plugin was chosen to provide the result of a data query. In this way, the service might be able to make future decisions on what or how to organize data in order to provide those types of requests more quickly in the future. For example, perhaps the Kerkopes plugin could collect metadata on a query so that it will reorder data available in intermediate cache for quicker response times. This type of data collection should always be optional (I think opt-out is reasonable), but I think it could dramatically improve the QoS that a plugin user might see in certain cases.
Specification
Change to:
Also, reiterate that all calls to this method should never fail so as not to stop the processing loop in
QueryManager
from functioning correctly, so all errors should be handled and logged if using this feature in this way to communicate to an external API service.Dependencies
n/a
The text was updated successfully, but these errors were encountered: