QueryTraversalManager.setBatchHint is never called.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Read the source.

What is the expected output? What do you see instead?

QueryTraverser.runBatch has a batchHint parameter that controls the maximum
size of the traversal, but it does not pass that along to the
QueryTraversalManager.

Please use labels and text to provide additional information.

It isn't documented whether setBatchHint is always called or not. Since it
isn't called, a connector must have a default value or it won't work at
all. If the default value is smaller than the runBatch parameter, there
will be more calls to runBatch, which is probably slightly inefficient. If
the default value is larger, then the connector is potentially doing
significantly more work to retrieve data that the QueryTraverser won't
consume. The effect is that the connector will retrieve data for some items
multiple times until they are eventually consumed by QueryTraverser.

Original issue reported on code.google.com by jl1615@gmail.com on 19 Jan 2007 at 10:00

[GoogleCodeExporter]

Brian, please add to backlog.

Original comment by donald.z...@gmail.com on 24 Jan 2007 at 11:49

• Changed state: Accepted

[GoogleCodeExporter]

Google Bug #243979

Original comment by vjo...@gmail.com on 9 Feb 2007 at 4:08

[GoogleCodeExporter]

Fixed in r435.

Original comment by mgron...@gmail.com on 3 Oct 2007 at 9:31

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by mgron...@gmail.com on 3 Oct 2007 at 10:49

• Added labels: Milestone-Release_1.0.0