Spark Streaming ETL jobs for Mozilla Telemetry
Перейти к файлу
Frank Bertsch 5847fb221e Setup travis ci deploy
* Deploy changes according to ops config
* Use ops artifact bucket
* Latest release as well as tagged releases
* Latest master as well as per-build master
* Make single reusable file
2018-04-25 14:47:08 -05:00
configs Add Android Focus eventsToAmplitude config 2018-03-28 11:21:39 -05:00
docker Add Integration Tests with Docker 2017-09-18 14:36:48 -05:00
project Bump sbt version to 1.1.1 2018-03-20 16:03:42 +01:00
src Make focus settings strings 2018-04-24 13:35:42 -05:00
.gitignore Add .gitignore 2017-01-24 17:34:02 +00:00
.travis.yml Setup travis ci deploy 2018-04-25 14:47:08 -05:00
README.md Bug 1423340 - Make tests easily runnable from IDE 2018-03-20 23:53:09 +01:00
build.sbt Bug 1449114 - Use scalastyle configuration hosted in moztelemetry repository 2018-03-28 22:34:18 +02:00
deploy.sh Setup travis ci deploy 2018-04-25 14:47:08 -05:00
docker_setup.sh Bug 1423340 - Make tests easily runnable from IDE 2018-03-20 23:53:09 +01:00

README.md

Build Status codecov.io

telemetry-streaming

Spark Streaming ETL jobs for Mozilla Telemetry

This service currently contains jobs that aggregate error data on 5 minute intervals. It is responsible for generating the (internal only) error_aggregates and experiment_error_aggregates parquet tables at Mozilla.

Issue Tracking

Please file bugs in the Datasets: Error Aggregates component.

Development

The recommended workflow for running tests is to use your favorite editor for editing the source code and running the tests via sbt. Some common invocations for sbt:

  • sbt test # run the basic set of tests (good enough for most purposes)
  • sbt "testOnly *ErrorAgg*" # run the tests only for packages matching ErrorAgg
  • sbt "testOnly *ErrorAgg* -- -z version" # run the tests only for packages matching ErrorAgg, limited to test cases with "version" in them
  • sbt dockerComposeTest # run the docker compose tests (slow)
  • sbt "dockerComposeTest -tags:DockerComposeTag" # run only tests with DockerComposeTag (while using docker)
  • sbt ci # run all tests

Some tests need Kafka to run. If one prefers to run them via IDE, it's required to run the test cluster:

sbt dockerComposeUp

or via plain docker-compose:

export DOCKER_KAFKA_HOST=$(./docker_setup.sh)
docker-compose -f docker/docker-compose.yml up

It's also good to shut down the cluster afterwards:

sbt dockerComposeStop