New features added to Google BigQuery:
- Big JOIN: use SQL-like queries to join very large datasets at interactive speeds
- Big Group Aggregations: perform groupings on large numbers of distinct values
- Timestamp: native support for importing and querying Timestamp data
I read with interest both the announcement and the technical (?) details post about the new SQL keyword
EACH introduced by BigQuery to perform
GROUP BY for “large tables”. Unfortunately I couldn’t find what’s behind this new keyword.
This made me think again of what’s wrong with SQL: almost every engine implementation detail bubbles up to the user creating a new flavor of SQL. Just think about it:
EACH has no meaning for either of these operations; is there a
NOTEACH JOIN?. But it was needed to instruct the engine to perform the operation differently.
Original title and link: Goolge BigQuery: JOIN and GROUPBY EACH. And Something Is Wrong With SQL ( ©myNoSQL)