**Context**:
> As we work on the Metrics Platform, trying to standardize how we ingest and capture common fields as well as consistently handle bespoke/custom fields, we will be introducing a new schema format. While designing the schema for bespoke/custom fields, we realize that if we want to support the ability to add and remove fields at-will, it may result in more effort to parse or query the data directly. Thus the Metrics Platform team would like to work with the Product Analytics team, to define a balance between the level of flexibility desired vs the ease-of-use when it comes to writing queries.
**What questions are we trying to answer?**
- Does querying become more difficult the more flexibly we handle bespoke/custom fields?
- Does flexibility of adding new fields take precedence over ease-of-use when querying?
- What is the balance we need to strike between flexibility and querying? "
**How long will this take?**
This should not take longer than 10-15 minutes.
**What are we testing?**
[[ https://docs.google.com/spreadsheets/d/1U8mjGzBeW6HkUaFM3akhSpfHeIoAubpXnpuOgzXTJnw/edit#gid=0 | The template ]] will ask you to write queries that answer some simple analytics questions based on 2 sample datasets provided in `jdl.demo`
We would like you to write the query in HiveQL (via [[ https://hue.wikimedia.org/ | Hue ]] or wmfdata) as well as Presto (via [[ https://superset.wikimedia.org/superset/sqllab/ | SQL Lab ]] or wmfdata) and ask you to copy and paste your answers into those columns.