Kingsley Idehen wrote: >> Then can you please explain how your normal run-off-the-mill SPARQL >> client implementing the SPARQL protocol can turn off "Anytime >> Queries"? It's not like I haven't asked this before, maybe I'll get an >> answer now :)
As it turns out, the answer to this question is "it doesn't need to". > If you recall, in the prior release of DBpedia we would return timeouts > for certain queries. Do you recall that behaviour? > > "Anytime Query" is about a new dimension that allows you to set timeouts > and retries so that you can do more. > > As with most things, in a few years time when "Anytime Query" is > implemented elsewhere by other Databases that offer query > parallelization, you will at least have a URI back to this thread :-) > There's nothing wrong with innovation. You seem to imply I am wrong - I am not. You simply missed my point :) > Also remember, I told you that the initial problem had zilch to do with > the "Antytime Query" feature, it had everything to do with an error in > the configuration of one of the cluster nodes. FWIW - cluster nodes are > about horizontal partitioning and query parallelization, so if a node is > mis-configured it can distort the behavior the whole. I realize that. I was solely reacting to the fact of Anytime Queries becoming the default - which was not true. Sorry 'bout the drama. Regards, Michael ------------------------------------------------------------------------------ _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
