Opened 8 years ago

Closed 8 years ago

#1630 closed enhancement (implemented)

Extend database schema by materialized views

Reported by: karsten Owned by: Karsten
Priority: High Milestone:
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The current database schema in ERNIE consists of tables and views. In order to support ad-hoc queries for dynamic graphs, we need to have materialized views plus a good concept to keep them updated. Update strategies range from (1) periodically re-generating the whole materialized views, (2) collecting changes on base tables and updating only those parts of materialized views that might have changed, and (3) triggering materialized view changes from table changes. While (1) is easiest to implement, it's infeasible for the amount of data in the database. (2) and (3) are harder to implement, but better fit the use case of having data covering multiple years in the database and adding data covering an hour or two. (2) is probably more efficient than (3), but even harder to implement. Kevin is working on this and might have results in July 2010.

Child Tickets

Change History (1)

comment:1 Changed 8 years ago by karsten

Resolution: implemented
Status: newclosed

Materialized views are implemented in the current database schema. We
decided to implement (2) "collecting changes on base tables and updating
only those parts of materialized views that might have changed".

Note: See TracTickets for help on using tickets.