Closed Bug 1197837 Opened 9 years ago Closed 9 years ago

Make sure Zenko can pull tile data from the new database

Categories

(Content Services Graveyard :: Tiles: Administration Front-End, defect, P1)

Product:
Content Services Graveyard
Component:
Tiles: Administration Front-End
Type:
defect
Points:
2

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Iteration:
43.2 - Sep 7

People

(Reporter: mruttley, Assigned: mruttley)

References

Details

The backend for tiles has just been split into two databases. It is essential that Zenko is able to access new information from the new database. 

This should just be at the caching stage.
Done https://github.com/matthewruttley/zenko/commit/7acec2c665ed0dc80ca0eb0d4dadce97e2215001
Status: NEW → RESOLVED
Points: --- → 2
Closed: 9 years ago
Resolution: --- → FIXED
Blocks: Sprint_CS_S2
Iteration: --- → 43.2 - Sep 7
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
There was an error pointed out by mstorm where zenko was trying to pull Casper data, but it couldn't join the tiles and impression_stats_daily table from both databases. 

I've fixed this with: https://github.com/matthewruttley/zenko/commit/8708656f2ae2118acfeeeb829eee0ce6e1e67fd4 which removes all but one tiles table INNER JOIN and replaces querying tile groupings with simply getting a list of relevant tiles from the cache. 
Removing this join should make the queries marginally faster as well.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.