search

azavea / osmesa-stat-server

temporary home of statistics server for processed OSM data
6 stars 3 forks source link

Move stats refresher tasks out of project #31

Open CloudNiner opened 4 years ago

CloudNiner commented 4 years ago

Given the state in #30, we are still actively using the stats-refresher tasks. They should be moved back to osmesa to consolidate the pieces we're actively using, esp given these tasks do work on the database.

jpolchlo commented 4 years ago

This is a slightly weird thing. Those materialized views are somewhat specialized to our use case and maaaaaybe don't belong here either? This is a weirdly specified project, and it's not clear what are the "core" principles. This is why we shunted the materialized views to this repo, since the stat server is the unequivocal consumer of that data. The tables set up by osmesa are general use, the ones here are in some sense derived stats.

The argument for maintaining the materialized views in osmesa go up if they are not, in fact, derived, but continuously updated by the streaming updaters (which would remove the need for a materialized view refresher task). See azavea/osmesa#139.

CloudNiner commented 4 years ago

Ah, thanks for the clarification. Sounds like it might be preferable to move to the repo handling our use case. But we can decide the resting place when this task is taken, as it doesn't necessarily increase task complexity.