Confirmed users
9,511
edits
EngineeringProductivity/Projects/ActiveData: Difference between revisions
EngineeringProductivity/Projects/ActiveData (view source)
Revision as of 05:34, 19 September 2019
, 19 September 2019→Overview
Klahnakoski (talk | contribs) (→Users: add uses) |
|||
| Line 4: | Line 4: | ||
ActiveData is a collection of about 8 billion records (Feb 2016) covering unit tests, Buildbot jobs, performance data, and mercurial. This collection is publicly available, and can be queried directly, similar to any database. | ActiveData is a collection of about 8 billion records (Feb 2016) covering unit tests, Buildbot jobs, performance data, and mercurial. This collection is publicly available, and can be queried directly, similar to any database. | ||
ActiveData is built on top of ElasticSearch, a fast, distributed, redundant document store. ActiveData provides the benefits of familiar and succinct SQL by translating SQL-like queries to ElasticSearch queries | ActiveData is built on top of ElasticSearch, a fast, distributed, redundant document store. ActiveData provides the benefits of familiar and succinct SQL by translating SQL-like queries to ElasticSearch queries. | ||
== Problem == | == Problem == | ||
| Line 11: | Line 11: | ||
== Solution== | == Solution== | ||
ActiveData will serve as a reusable ETL pipeline; annotating the test results with as much relevant data as possible. It also provides a query service to explore and aggregate the data, so there is minimal setup required to access this data. | ActiveData will serve as a reusable ETL pipeline; annotating the test results with as much relevant data as possible. It also provides a query service to explore and aggregate the data, so there is minimal setup required to access this data. | ||
= Redash = | = Redash = | ||