Hi Henrik,
The “MaxQueryCostEstimationTime"param should never be set in the INI file in
production use as it is used for Cost Optimizer estimates and are generally
not accurate and is more a development/debug param. Thus the only one that
should be set to control query execution time is “MaxQu
Hi,
is there a way to make good use of MaxQueryCostEstimationTime to prevent
extremly long running queries ?
For the 'real' SELECT query we want to use the jena provider but the
idea is to first ask the SPARQL port to check whether the query is
immediately rejected due to MaxQueryCostEstimat
