Using Block Nested Loop Join, with different memSize values can cause redundant
tuples, being generated by the operator.
An example:
Using TPC-H Join, with a scale factor of 2 for the size, on (Cust join Orders),
in the current JUnit test "TPCHCustomerOrderNestedLoopJoinTest", with memSizes
of 15 or 100, instead of 4000, generates extra tuples.
Original issue reported on code.google.com by pouria.p...@gmail.com on 19 May 2011 at 12:45
Original issue reported on code.google.com by
pouria.p...@gmail.com
on 19 May 2011 at 12:45