the pseudo query planner uses a table, in which all classes specified in the domain are queried on all applicable endpoints, to get the total number of results and the elapsed time. This data is used to reorder the query components. However, today it is hardcoded.
We need an option to use a custom table (provided by the user or generated, as described in another issue), or no planning at all.
the pseudo query planner uses a table, in which all classes specified in the domain are queried on all applicable endpoints, to get the total number of results and the elapsed time. This data is used to reorder the query components. However, today it is hardcoded.
We need an option to use a custom table (provided by the user or generated, as described in another issue), or no planning at all.