Eventually consistent external materialized views.
(Note: Originally a fork of https://github.com/kirasystems/views)
Gered
78feb25839
another potentially contentious change. the idea here is based on my inability to come up with a reason why each library providing an IView implementation (e.g. views-honeysql) would need a different function for this. in fact, i'd argue that it's probably a better idea to have all the hints going to a single "dispatch" function anyway (aka. this put-hints-fn) and have it check for any metadata on incoming hints and do any custom processing there. the IView implementation libraries have this ability already to add any kind of custom metadata to hints anyway. i don't think anything is lost by this change personally, and it removes the need to call multiple functions to set a custom put-hints-fn for each IView library that a project might need. tl;dr - i like simpler configuration. this change is the beginning of stuff that helps me do that in the future. |
||
|---|---|---|
| src/views | ||
| test/views | ||
| .gitignore | ||
| .travis.yml | ||
| LICENSE | ||
| NOTES.md | ||
| project.clj | ||
| README.md | ||
views
Eventually consistent external materialized views.
Notice: library is still somewhat in flux.
Design
TODO
Usage
TODO
Testing
TODO
License
Copyright © 2015-2016 Kira Inc.
Authors Dave Della Costa (https://github.com/ddellacosta) and Alexander Hudek (https://github.com/akhudek)
Distributed under the MIT License.