Am 11.02.2016 um 10:17 schrieb Gerard Meijssen:
Your response is technical and seriously, query is a
tool and it should function
for people. When the tool is not good enough fix it.
What I hear: "A hammer is a tool, it should work for people. Tearing down a
building with it takes forever, so fix the hammer!"
The query service was never intended to run arbitrarily large or complex
queries. Sure, would be nice, but that also means committing an arbitrary amount
of resources to a single request. We don't have arbitrary amounts of resources.
We basically have two choices: either we offer a limited interface that only
allows for a narrow range of queries to be run at all. Or we offer a very
general interface that can run arbitrary queries, but we impose limits on time
and memory consumption. I would actually prefer the first option, because it's
more predictable, and doesn't get people's hopes up too far. What do you think?
Oh, and +1 for making it easy to use WDT on labs.
Senior Software Developer
Gesellschaft zur Förderung Freien Wissens e.V.