The bug seems to occur in 3.1 & devel (not 3.0) when using the cursor API 
to fetch more documents than are fitting into the initial batch (default 
batchSize is 1000).
A fix for this is in progress.
Best regards

Am Mittwoch, 12. Oktober 2016 11:34:03 UTC+2 schrieb Jan:
> Hi Rob,
> obviously this is not intentional.
> We have tried reproducing this in 3.0 & devel, but with no luck yet.
> I am a bit puzzled because you mention that it is ArangoDB 3.0.10 showing 
> that issue. The 3.0 branch does and never contained the string 
> "DefaultCustomTypeHandler". I remember that code being added to devel, so 
> it may have got into the 3.1 branch, but not 3.0. Can you confirm the 
> problem is actually occurring in an ArangoDB 3.0? And could you please 
> provide the query that triggers the problem?
> Thanks
> Jan
> Am Mittwoch, 12. Oktober 2016 10:58:53 UTC+2 schrieb Rob Keevil:
>> Hi,
>> I am using arangoDB 3.0.10 and arangodb-java-driver 3.0.3 (latest 
>> stable).  I've written a java connector in my application, which is using 
>> arangoDriver.executeAqlQueryRaw to return a cursor of Json documents as 
>> Strings.
>> My input collection contains some single-level Json documents, where all 
>> fields in the document are quoted strings (e.g. "business_address_city": 
>> "├ůMLI" ). My query is returning all documents in the collection.
>> For every document returned, arangoDB logs in the console:
>> 2016-10-12T08:21:02Z [1] WARNING DefaultCustomTypeHandler called
>> As well as being messy, i think this is really affecting the performance 
>> of my application when selecting millions of documents.  Can anyone give me 
>> some pointers on what is happening?
>> Thanks,
>> Rob

You received this message because you are subscribed to the Google Groups 
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to