I was (mostly still am) a big fan of Google BigQuery. Especially since GQL supported some Regex, plus native URL parsing. That is one of the coolest services that Google offers that no other service can match.
However, having used Big Query extensively at my startup, getting external data into it via Google Cloud Storage was a royal pain in my balls.
My broader point, is that Google was able to disrupt the Ad industry because it dominated web search by way of having a large number of exceptionally brilliant engineers. In 2016, that is no longer true--many other big (and small) players have invested in hiring their own equally brilliant engineers.
Sorry to hear. We have completely revamped our ingest mechanism lately. Feel free to ping me with specific problem you had.
From my experience, most issues with loading data stem from just data parsing, or trying to make batch load behave like stream load (we have an api for that too).
And, one of the things I mention in my article, unlike any other database, batch ingest into BigQuery is entirely free, as in not competing with query capacity one bit.
However, having used Big Query extensively at my startup, getting external data into it via Google Cloud Storage was a royal pain in my balls.
My broader point, is that Google was able to disrupt the Ad industry because it dominated web search by way of having a large number of exceptionally brilliant engineers. In 2016, that is no longer true--many other big (and small) players have invested in hiring their own equally brilliant engineers.