...
- Currently data-pumps, event-based or otherwise, are considered out of scope. Should alternative 1 to the problem above be considered, then this should be re-evaluated for certain data, with an eye to keeping LOE low. E.g. Data pumps could help reduce the cons of this approach listed above regarding report fragility as well as Service databases needing to be co-located in the same PostgreSQL cluster. The most basic data pump may look like:
Gliffy imageAttachmentId att112742241 baseUrl https://openlmis.atlassian.net/wiki size 300 migration 1 name Simple Data Pump (ETL) diagramAttachmentId att112742237 containerId 112496858 - Jaspersoft Server, which could help us with report filters, scheduling, etc is considered out-of-scope. We should re-visit this when we'd like these additional features / desire to have a less hack-y filtering solution.
...
- Josh Zamor and Paweł Nawrocki (Deactivated) to sync on mw-reports
- Josh Zamor to update diagram to go with alternative 1 (SQL over Java Beans)
- Josh Zamor, Paweł Nawrocki (Deactivated), and Jakub Kondrat to sync again after Service is built and reports are available - we'll look again at functionality plus design and pull into product