This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hi all,We are wanting to create a Dataform model that combines all of
the BigQuery INFORMATION_SCHEMA.JOBS data from multiple projects into
one table. The way we do this in pure SQl would effectively be
like:SELECT * FROM `..INFORMATION_SCHEMA.JOBS`
...
I am wanting to use the Looker System Activity models in our own model
in LookML in order to combine it with other sources, but wondering if
this is possible.Specifically, one example of what I am trying to do is
that I've got the BigQuery InfoSchema...
Hi there,I am wanting to try and avoid using an UNNEST function to
access some array data due to the fact that it would explode out into
duplicates, when all I actually care about is the first element of the
array.So I am trying to find out if there ...
Hi there,As analytics engineers, we want to be able to tag our dataform
queries by the layer and domain so that we can see how much each layer
and domain costs us (using the info schema).We initially thought we
could do this via the BigQuery labels c...
Hi there,We are on on-demand billing (billed per bytes processed).We are
finding that when we run the recommended setup for incremental models on
dataform ( WHERE date > (SELECT MAX(date) FROM ${self()}) ) then there
is no difference between bytes pr...
Thanks Andy, I think we did try this GSheet workflow initially, but I
think we were stuck with issues about row limits (as we have up to 25k
history slugs per day). However, I think we've actually recently
discovered that's a simple permissions chang...
Thanks Andy, will pop it in Product Ideas.Seems like for my very simple
main use case of wanting a lookup of Looker User IDs, it's probably
easiest to just maintain a GSheet lookup vs overcomplicating by setting
up a pseudo-pipeline. But may look at ...
Ahhhh, it will be because of the dataform version. We have 2.0.1, and we
definitely don't have any of those labels. We'll look to upgrade.Still
not convinced on if it's valuable, though. Seems to just give the same
as what the destination_table gives...
This sounds interesting, but yeh not very granular and potentially just
similar to the detination table data that is already there.But, sorry,
where do you see this? I'm going into the "Job Explorer" section,
clicking on one of the Job IDs to pull up...
So interestingly, the query you provided does indeed work, however, it
doesn't work when we apply it to our actual data (just comes out with
NULLs). After investigation it appears the data type is actually a
record/array, and therefore similar (but s...
