Thanks for your reply




________________________________
From: Patrick van Kleef <[email protected]>
To: sareh aghaei <[email protected]>
Cc: [email protected]
Sent: Fri, June 24, 2011 2:20:58 PM
Subject: Re: [Dbpedia-discussion] default limitation for fetching triples from 
dbpedia endpoint

Hi Sareh,

> 
> Is there any default limitation in sparql queries from dbpedia 
>endpoint?(http://dbpedia.org/sparql)
> I think the maximum of triples that can be fetched is 2000 triples for every 
>query, how can I omit this limitation?
> I'll be so pleased for your helping

The http://dbpedia.org/sparql endpoint has both rate limiting on the number of 
connections/sec you can make, as well as restrictions on resultset and query 
time, as per the following settings:

   [SPARQL]
   ResultSetMaxRows           = 2000
   MaxQueryExecutionTime      = 120
   MaxQueryCostEstimationTime = 1500


These are in place to make sure that everyone has a equal chance to 
de-reference 
data from dbpedia.org, as well as to guard against badly written queries/robots.

The following options are at your disposal to get round these limitations:

1. Use the LIMIT and OFFSET keywords

   You can tell a SPARQL query to return a partial result set and how many 
records
   to skip e.g.:

    select ?s where { ?s a ?o }
    LIMIT 1000 OFFSET 2000


2. Setup a dbpedia database in your own network

   The dbpedia project provides full datasets, so you can setup your own 
installation
   on a sufficiently powerful box using Virtuoso Open Source Edition.


3. Setup a preconfigured installation of Virtuoso + database using Amazon EC2 
(not free)

   See: http://www.openlinksw.com/dataspace/dav/wiki/Main/VirtAWSDBpedia351C


Please let me know if you have any questions on this or any other dbpedia 
sparql 
endpoint issue.


Best regards,

Patrick
----
OpenLink Software
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a 
definitive record of customers, application performance, security 
threats, fraudulent activity and more. Splunk takes this data and makes 
sense of it. Business sense. IT sense. Common sense.. 
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to