(see issue #4 )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.
in this issue, we need to implement a profiler, which will run all those queries in all these endpoints to generate a file, which will be used in #4.
(see issue #4 )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.
in this issue, we need to implement a profiler, which will run all those queries in all these endpoints to generate a file, which will be used in #4.