...
Besides, we would add integration tests for connectors to verify it can cooperate with existing source/sink implementations.
Other Alternatives
Hint Syntax
We could use name 'SHUFFLE_HASH' just like spark[2] sql.
Code Block | ||
---|---|---|
| ||
SELECT /*+ SHUFFLE_HASH('Orders', 'Customers') */ o.order_id, o.total, c.country, c.zip
FROM Orders AS o
JOIN Customers FOR SYSTEM_TIME AS OF o.proc_time AS c
ON o.customer_id = c.id; |
SQL Server[3] uses keyword 'hash' instead of query hint, it's not a good choise for use, so we ignore this.
Implementation
There is a simpler but a little hack solutionimplementation, this is also what we apply in the internal version.
...
Anyway, the difference between the two solution is only about the internal implementation and has no impact on the user.
Reference
[1] Oracle Hash Join hinthint syntax
[3] SQL Server Hash Keyword syntax