Issue #20 - Hash join implementations

[maryannxue]

The main impact on interfaces in the current master:

1. QueryCompiler: the original logic of compile() now goes into compileSingleQuery(), and the call compile() is now used as entry for both single select statements and join statements. Join statement compilation might go through recursive calls of compileSingleQuery() and compileJoinQuery().
2. ServerCacheClient: the original interface takes a TableRef in the constructor, while the parameter has now been moved to addServerCache(), for the reason that we might want to reuse ServerCacheClient for multiple calls in completing a query, and the parameter "cacheUsingTableRef" could be different among these multiple calls.

[jtaylor-sfdc]

Subtle difference between these two. Should be:

  if (hasValue == null) {
      return false; // expression could not be evaluated
  }
  if (!hasValue.booleanValue()) {
        return true; // expression was evaluated, but evaluated to null
  }

[jtaylor-sfdc]

Fantastic job, @maryannxue. Please add javadoc, comments, and respond to the above minor comments on a followup pull request. So excited to have hash joins now! We'll give it some perf testing and let you know what we find out.

[maryannxue]

Will do. Really appreciate these very detailed comments, James!