Aklakan commented on issue #1477: URL: https://github.com/apache/jena/issues/1477#issuecomment-1250946972
It's a bug in the test; the configured limit does not consider the farthest possible read ahead until the queue blocks because of becoming full. The justification for 60K bytes is as follows: - Chunk size is set to 100, one triple in the test is always exactly 50 bytes - so one chunk corresponds to 5000bytes. - The queue size is 10 - so it can hold 50K, after that it blocks. - However, we consume 10 triples which removes one chunk, which gets filled up again - at this point we consumed 55K. - Then we abort, which clears the queue and schedules abort on the next chunk. When it arrives 60K have been consumed. So the read ahead in the test is `(queueSize + 2) * (chunkSize * tripleByteSize)`. If the parser used buffering then a bit more could be read. But e.g. setting the limit in the test to e.g. 70.000 should fix it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
