Create gerrit repository for the Editor Analytics service, using the other AQS 2.0 service repositories as an example. Populate with the Go service scaffolding as a starting point, with boilerplate suitably modified as necessary.
Completion criteria: the repository is ready to accept merge requests for endpoint and unit test implementation.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| First approach for a Druid-base AQS 2.0 endpoint | generated-data-platform/aqs/editor-analytics | main | +833 -370 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T324931 Clean up open RESTBase related tickets | |||
| In Progress | None | T262315 <CORE TECHNOLOGY> API Migration & RESTbase Sunset | |||
| In Progress | DAbad | T263489 AQS 2.0 | |||
| Resolved | None | T327818 Editor Analytics Service | |||
| Resolved | EChukwukere-WMF | T327826 AQS 2.0: Editor Analytics: Create and initialize gerrit repository |
Change 922163 had a related patch set uploaded (by Santiago Faci; author: Santiago Faci):
[generated-data-platform/aqs/editor-analytics@main] [DNM] First approach for a Druid-base AQS 2.0 endpoint
Previous patch is not definitive. It has been made to be able to review some changes to start discussing about the right way to deal with Druid and create reusable code for the two services that use this database engine
Change 922163 abandoned by Santiago Faci:
[generated-data-platform/aqs/editor-analytics@main] [DNM] First approach for a Druid-base AQS 2.0 endpoint
Reason:
no longer needed. About to push a new valid MR
Change 922163 restored by Santiago Faci:
[generated-data-platform/aqs/editor-analytics@main] [DNM] First approach for a Druid-base AQS 2.0 endpoint
Change 922163 merged by BPirkle:
[generated-data-platform/aqs/editor-analytics@main] First approach for a Druid-base AQS 2.0 endpoint
Change merged with the understanding (per separate discussion) that this code is somewhat speculative and significant work remains to make it production ready. But this is a great start!
QA: don't worry about integration tests (make itest) or hitting the endpoint in your browser - you'd need new data in the Druid mock dataset and that's not ready yet. It is sufficient to confirm that these succeed: