Telemetry/LongitudinalExamples: Difference between revisions

Jump to navigation Jump to search
Adding note about DESCRIBE operator
(Filling out resources section)
(Adding note about DESCRIBE operator)
Line 5: Line 5:


Get an overview of the longitudinal data table:
Get an overview of the longitudinal data table:
  describe longitudinal
  DESCRIBE longitudinal


That table has a row for each client, with columns for the different parts of the ping.
That table has a row for each client, with columns for the different parts of the ping.
There are a lot of fields here, so I recommend downloading the results as a CSV if you want to search through these fields.
Unfortunately, there's no way to filter the outputof DESCRIBE in Presto.
Some properties are directly available to query on:
Some properties are directly available to query on:
  SELECT count(*) AS count
  SELECT count(*) AS count
Line 90: Line 93:
  CREATE OR REPLACE VIEW view_name AS ...
  CREATE OR REPLACE VIEW view_name AS ...
Be careful not to overwrite an existing view! Using a unique name is important.
Be careful not to overwrite an existing view! Using a unique name is important.
Find more information [https://prestodb.io/docs/current/sql/create-view.html here].
=== Other Resources ===
* [https://prestodb.io/docs/current/sql.html Presto Docs]
* [https://github.com/mozilla/telemetry-batch-view/blob/master/src/main/scala/com/mozilla/telemetry/views/Longitudinal.scala#L194 Longitudinal schema definition]
* [[Custom_dashboards_with_re:dash]]


=== FAQ ===
=== FAQ ===
==== I'm getting an error, "... cannot be resolved" ====
==== I'm getting an error, "... cannot be resolved" ====
For some reason, re:dash has trouble parsing SQL strings with double quotes. Try using single quotes instead.
For some reason, re:dash has trouble parsing SQL strings with double quotes. Try using single quotes instead.
54

edits

Navigation menu