Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently the big table is always assumed to be at position 0 but this isn't efficient for some queries as the big table at position 1 could have a lot more keys/skew. We already have a mechanism of choosing the big table that can be leveraged to make the right choice.