There is no hash join in Teiid.  Are you trying to push down a hint or have Teiid evaluate a hash join?  In the latter case Teiid typically relies on costing to determine the join strategy which can include performing an enhanced sort merge join which can optionally sort the smaller relation and use it as a lookup index for the other side.

Define choke, and what are you seeing as the query plan, and have you set at least the cardinalities on the relevant tables?

To expand on the last comment. When tables being joined from different sources are unbalanced, then most of the time you would want what is called a dependent join to be performed.  This will filter the larger side against the equi join values from the other side rather than pulling all of the rows.  However we will only plan a dependent join based upon costing information or a hint.  That is why the table cardinalities are important.  Beyond that if there is still an imbalance that is where the enhanced sort merge join comes into play.