5847fb221e
* 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 |
||
---|---|---|
configs | ||
docker | ||
project | ||
src | ||
.gitignore | ||
.travis.yml | ||
README.md | ||
build.sbt | ||
deploy.sh | ||
docker_setup.sh |
README.md
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