4 ms·
It has joins now, but Google says this: "Joins have size restrictions due to implementation details. Essentially it means that the data on both sides of the JOI
by epaulson 15y ago
It has joins now, but Google says this: "Joins have size restrictions due to implementation details. Essentially it means that the data on both sides of the JOIN clause cannot be large. For example, select count() FROM big_table JOIN another_big_table will fail, but select count() FROM big_table JOIN small_table will succeed. Because this size restriction depends on many complex variables, the best way to handle joins is to try your join, and if it returns a "Table too large for JOIN query" error, limit the data handled by join clauses by specifying fewer fields or rows."
If someone is in the pilot, I'd love to know some different table/result set cardinalities where you hit the "too large for join" limit, as well as what your data and join conditions look like.
- ameyamk 15y agoI was taken aback by support for 'JOIN' but this comment makes me less excited about the service.
- rxin 15y agoSupport for joining two very large tables is nice, but isn't really a super big deal. In a typical warehouse star schema, you have a very very large fact table, and a number of dimension tables. The dimension tables tend to be small.
- jukaykwek 15y agoThat's the general idea. At least for the current release we prioritized a more common case ilke what rxin describes. That said, if you have a "big join" use case, please sign up for the wait list (http://goo.gl/7zpSn http://goo.gl/7zpSn) and specifically list your use case. We'd like to talk to you about that. :)