フリー問題

問題文

A manufacturing team joins two tables whose sizes the catalog does not know. The plan printed before the run shows a sort merge join, but the screen after the run shows a different strategy for the same query. What did the framework do?

選択肢

1. At runtime the framework can switch a sort merge join to the range partitioned merge when one side turns out to be small.
2. At runtime the framework can switch a sort merge join to the shuffled nested loop when one side turns out to be small.
3. At runtime the framework can switch a sort merge join to the broadcast hash join when one side turns out to be small.
4. At runtime the framework can switch a sort merge join to the cartesian product scan when one side turns out to be small.