Hi,
I reorganized my query as you say, using one of filter (FILTER IN)
method. The query, that I send my local drugbank endpoint contains 4348
element in its filter block. I have tried several scenarios as configuring
the element count in filter block. When element count in filter block is
bigger
Hi Burak,
Presumably you are not creating these queries by typing them into a web
browser form? But instead have written code that does a HTTP GET request
to the SPARQL endpoint?? In which case, as Patrick has suggested, use
POST instead of GET -- the request needs a Content-type of
Hello,
How do I configure incoming HTTP request size in Virtuoso server(opensource
6.1)? I cannot send queries which are greater than a few kilobytes (25 KB).
Thanks you.
Burak Yönyül
--
LogMeIn Rescue: Anywhere,
Hi,
I cannot execute queries which are greater than a few kilobytes on
Virtuoso. I've loaded example drugbank dataset into Virtuoso Opensource 6.1
and I'm trying to execute the query in the file I've attached here, on my
local drugbank dataset with the sparql endpoint
Hello Burak Yönyül,
I cannot execute queries which are greater than a few kilobytes on Virtuoso.
I've loaded example drugbank dataset into Virtuoso Opensource 6.1 and I'm
trying to execute the query in the file I've attached here, on my local
drugbank dataset with the sparql endpoint
Hello Burak Yönyül,
I cannot execute queries which are greater than a few kilobytes on Virtuoso.
I've loaded example drugbank dataset into Virtuoso Opensource 6.1 and I'm
trying to execute the query in the file I've attached here, on my local
drugbank dataset with the sparql endpoint
Hello Burak
If you want to get tens of result columns, not a long narrow result set
for all,
then you can simply remove extra nesting from your original query.
You can put all UNION mambers to one level. Even if UNION is specified
in the SPARQL spec as a binary operation you don't have to write
Hello all,
Thank you for your suggestions. I will take your opinions into account.
There are possible ways to shorten query with better ordering of UNION
blocks as you say. But we use queries much more union count than this, so
the query size will grow into a few megabytes. Is there any way to
