Feat/boost v3 #2471
Ticket(s) / Related Merge Requests
Summary of Changes
- Introduces a new boost v3 module
- A ranking system for boosts
Testing Considerations
Deployment Considerations
Schemas
Deploy the following schemas.
CREATE TABLE IF NOT EXISTS boosts
(
guid bigint PRIMARY KEY,
owner_guid bigint NOT NULL,
entity_guid bigint NOT NULL,
target_suitability int NOT NULL,
target_location int NOT NULL,
payment_method int NOT NULL,
payment_amount float NOT NULL,
payment_tx_id text NULL DEFAULT NULL,
daily_bid float NOT NULL,
duration_days int NOT NULL,
status int NOT NULL,
created_timestamp timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated_timestamp timestamp NULL DEFAULT NULL,
approved_timestamp timestamp NULL DEFAULT NULL,
INDEX (owner_guid),
INDEX (entity_guid),
INDEX (target_location),
INDEX (payment_method),
INDEX (created_timestamp)
) ENGINE=InnoDB;
CREATE TABLE IF NOT EXISTS boost_summaries
(
guid bigint PRIMARY KEY,
day int NOT NULL,
views int NOT NULL,
reach int NOT NULL
) ENGINE=InnoDB;
CREATE TABLE IF NOT EXISTS boost_rankings
(
guid bigint PRIMARY KEY,
ranking_open float,
ranking_safe float,
last_updated timestamp
) ENGINE=InnoDB;
Config map changes
Make sure helm-charts!111 (merged) is merged
Setup the ranking runner
Make sure the php cli.php Boost rank
job is running as a deployment.
Feature
The feature flag should be disabled until we are ready to release. We are using the epic-293-dynamic-boost
flag.
Regression Scope
This only impacts the new boost system and is isolated from the v2 boost system.
Platform Affected (web, mobile, etc)
Web/API
Developer Testing Completed
In progress
Screenshots / Screen Recording
Does this impact
-
Localization -
Dark/light mode -
Guest mode
Definition of Done Checklist
-
The Acceptance Criteria has been met -
Code is tested: Testing includes unit/spec, E2E/automated and manual testing -
Merge requests description has been filled out
Edited by Fausto Arcidiacono