Re: [Virtuoso-users] SPARQL query size limits (GET, POST, POST DIRECT)
Hi, On 7 Apr 2015, at 01:48, Hugh Williams hwilli...@openlinksw.com wrote: 10K is the maximum limit, see the following post: http://boards.openlinksw.com/phpBB3/viewtopic.php?f=12t=1377#p4422 in that thread you mention a 10 K limit (of bytes i assume) for GET. What are the limits for POST and POST DIRECT? Cheers, Jörn On 4 Apr 2015, at 18:45, Jörn Hees j_h...@cs.uni-kl.de wrote: Hi, for my PhD (learning graph patterns for human associations) i'm currently experimenting with some sub-graphs that i need to match via SPARQL against a Virtuoso endpoint. The sub-graph sizes range from 30 to 400K triples and are automatically transformed into SPARQL queries (basically via N3). I'm interested in the practical limits for queries via: - GET - POST - POST DIRECT in terms of bytes, chars and triples. I noticed that there seems to be a 1 line limit for the SQL query that is the outcome of the SPARQL query. I'm not sure how SPARQL queries are translated into SQL lines though... is this triple wise (so max 1 triples) or term wise (so max 1/3 triples) or something else? Experiments tell me that the GET method seems to have a ~1 byte limit (after urlencoding). Sadly, I couldn't really test POST DIRECT, as on our local 7.1.0 endpoint even queries with ~150 triples (~18000 chars) seem to crash the endpoint :( If i remove long literals (which also happen to contain a lot of unicode chars), the query doesn't return within 2 hours. If i switch to POST query, i only get a Virtuoso 42000 Error SR483: Stack Overflow error, but the server keeps running at least... If for POST queries i keep the urlencoded query size 1 bytes, it seems to work. Running the POST DIRECT query against http://dbpedia.org/sparql results in an HTTP Error 409: Invalid path. POST gives me Virtuoso 37000 Error SP031: SPARQL: Internal error: The length of generated SQL text has exceeded 1 lines of code If I run the 1 byte POST it seems to work again... Can anyone confirm my findings / give me a recommendation for how big a sane query can get? Cheers, Jörn -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
Re: [Virtuoso-users] SPARQL query size limits (GET, POST, POST DIRECT)
Hi Jörn, 10K is the maximum limit, see the following post: http://boards.openlinksw.com/phpBB3/viewtopic.php?f=12t=1377#p4422 http://boards.openlinksw.com/phpBB3/viewtopic.php?f=12t=1377#p4422 Best Regards Hugh Williams Professional Services OpenLink Software, Inc. // http://www.openlinksw.com/ Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers On 4 Apr 2015, at 18:45, Jörn Hees j_h...@cs.uni-kl.de wrote: Hi, for my PhD (learning graph patterns for human associations) i'm currently experimenting with some sub-graphs that i need to match via SPARQL against a Virtuoso endpoint. The sub-graph sizes range from 30 to 400K triples and are automatically transformed into SPARQL queries (basically via N3). I'm interested in the practical limits for queries via: - GET - POST - POST DIRECT in terms of bytes, chars and triples. I noticed that there seems to be a 1 line limit for the SQL query that is the outcome of the SPARQL query. I'm not sure how SPARQL queries are translated into SQL lines though... is this triple wise (so max 1 triples) or term wise (so max 1/3 triples) or something else? Experiments tell me that the GET method seems to have a ~1 byte limit (after urlencoding). Sadly, I couldn't really test POST DIRECT, as on our local 7.1.0 endpoint even queries with ~150 triples (~18000 chars) seem to crash the endpoint :( If i remove long literals (which also happen to contain a lot of unicode chars), the query doesn't return within 2 hours. If i switch to POST query, i only get a Virtuoso 42000 Error SR483: Stack Overflow error, but the server keeps running at least... If for POST queries i keep the urlencoded query size 1 bytes, it seems to work. Running the POST DIRECT query against http://dbpedia.org/sparql results in an HTTP Error 409: Invalid path. POST gives me Virtuoso 37000 Error SP031: SPARQL: Internal error: The length of generated SQL text has exceeded 1 lines of code If I run the 1 byte POST it seems to work again... Can anyone confirm my findings / give me a recommendation for how big a sane query can get? Cheers, Jörn -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
[Virtuoso-users] SPARQL query size limits (GET, POST, POST DIRECT)
Hi, for my PhD (learning graph patterns for human associations) i'm currently experimenting with some sub-graphs that i need to match via SPARQL against a Virtuoso endpoint. The sub-graph sizes range from 30 to 400K triples and are automatically transformed into SPARQL queries (basically via N3). I'm interested in the practical limits for queries via: - GET - POST - POST DIRECT in terms of bytes, chars and triples. I noticed that there seems to be a 1 line limit for the SQL query that is the outcome of the SPARQL query. I'm not sure how SPARQL queries are translated into SQL lines though... is this triple wise (so max 1 triples) or term wise (so max 1/3 triples) or something else? Experiments tell me that the GET method seems to have a ~1 byte limit (after urlencoding). Sadly, I couldn't really test POST DIRECT, as on our local 7.1.0 endpoint even queries with ~150 triples (~18000 chars) seem to crash the endpoint :( If i remove long literals (which also happen to contain a lot of unicode chars), the query doesn't return within 2 hours. If i switch to POST query, i only get a Virtuoso 42000 Error SR483: Stack Overflow error, but the server keeps running at least... If for POST queries i keep the urlencoded query size 1 bytes, it seems to work. Running the POST DIRECT query against http://dbpedia.org/sparql results in an HTTP Error 409: Invalid path. POST gives me Virtuoso 37000 Error SP031: SPARQL: Internal error: The length of generated SQL text has exceeded 1 lines of code If I run the 1 byte POST it seems to work again... Can anyone confirm my findings / give me a recommendation for how big a sane query can get? Cheers, Jörn -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
