-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Matched captures statistic #73
Conversation
@@ -2,8 +2,8 @@ const BaseRepository = require('./BaseRepository'); | |||
|
|||
class CaptureRepository extends BaseRepository { | |||
constructor(session) { | |||
super('capture_denormalized', session); | |||
this._tableName = 'capture_denormalized'; | |||
super('reporting.capture_denormalized', session); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should remove the 'reporting.'. In the cloud, the DATABASE_URL is already configured only to access the reporting schema, so this is unnecessary. This might also be the reason for the failed tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, my bad. I thought I committed the code without the reporting.
prefix.
@@ -55,6 +55,7 @@ class CaptureRepository extends BaseRepository { | |||
const whereBuilder = function (object, builder) { | |||
const result = builder; | |||
const filterObject = { ...object }; | |||
console.log('FILTEROBJ', filterObject) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can remove the console.log
🎉 This PR is included in version 1.9.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
A new reporting card statistic for matched captures is implemented.
Issue(s) addressed
What kind of change(s) does this PR introduce?
Please check if the PR fulfils these requirements
Issue
What is the current behavior?
There is no matched captures statistic.
What is the new behavior?

The
capture/statistics
andcapture/statistics/card?card_title=matched_captures
endpoints returnmatched_captures
statistic.Breaking change
Does this PR introduce a breaking change?
No.
Other useful information
The image for new behavior is based on test data. The
capture_denormalized
table needs to be populated using an Airflow task, which is not yet updated.