The SPARQL QUERY specifies a different behavior than you are expecting. The following clearly indicates that LIMIT is defined in terms of solutions, not the triples returned by a DESCRIBE.
The LIMIT clause puts an upper bound on the number of solutions returned. If the number of
actual solutions, after OFFSET is applied, is greater than the limit, then at most the limit
number of solutions will be returned.
For some community messages about this see:
- See http://lists.w3.org/Archives/Public/public-lod/2009Sep/0041.html
Bigdata allows you to specify query hints that are intended to shape the behavior of DESCRIBE. See the QueryHints interface (http://www.bigdata.com/docs/api/com/bigdata/rdf/sparql/ast/QueryHints.html). In particular, look at:
static String DESCRIBE_ITERATION_LIMIT
For iterative DescribeModeEnums, this property places a limit on the number of iterative expansions that will be performed before the DESCRIBE query is cut off, providing that the limit on the maximum #of statements in the description is also satisfied (the cut off requires that both limits are reached).
static String DESCRIBE_MODE
Query hint controls the manner in which a DESCRIBE query is evaluated.
static String DESCRIBE_STATEMENT_LIMIT
For iterative DescribeModeEnums, this property places a limit on the number of statements that will be accumulated before the DESCRIBE query is cut off, providing that the limit on the maximum #of iterations in the description is also satisfied (the cut off requires that both limits are reached).
Also see this wiki page about the use of query hints in bigdata:
I am going to close this ticket as invalid. Bigdata is implementing the correct behavior per the SPARQL specification as cited above.