On 04/17/2012 05:32 AM, Quentin wrote:
Hi,
I'm doing a sponge of a large JSON file using a custom cartridge and if
I turn TRACE_ON() then somewhere during the import, I'm seeing pages and
pages of errors that look like:
"02:49:56 ERRS_0 42001 XPQ?? Magnitude is too big (950061485) to be
pack
Hi
How are you connecting to your Virtuoso instance is this via the Virtuoso
ADO.Net Provider ie SQL port or via the SPARQL endpoint ie HTTP port ?
There is such a limit on the SPARQL Endpoint but not when querying via the
ADO.Net Provider.
It there a reason why you want to query 1M+ rows at
I tried with more than one query that should definitely return more than 2M
results , it appears that virtuoso hardlimits the result max rows to this
number overriding any parameters I give in the virtuoso.ini file.
it's even limited by that number in dotNetRDF library
any workaround on that ?
Hi,
I'm doing a sponge of a large JSON file using a custom cartridge and if I
turn TRACE_ON() then somewhere during the import, I'm seeing pages and
pages of errors that look like:
"02:49:56 ERRS_0 42001 XPQ?? Magnitude is too big (950061485) to be
packed into int"
It doesn't seem to hurt the