-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick TimeSeriesDatabase from megacarbon branch #484
Cherry-pick TimeSeriesDatabase from megacarbon branch #484
Conversation
Thanks, I'll try and take a look at this today
|
OK, thanks. FYI, I've finished the conversion here: master...iain-buclaw-sociomantic:tsdatabase2 Doing some small tests and it all works fine with both whisper and ceres. |
Rebased, and fiddled with the |
Note: when I say "I'll look at this today" it often means "I'll start feeling guilty about not looking at this starting today" ;) I promise I haven't forgotten about this. This is something that has needed to be done for some time, thanks for the work! |
I can kindof go either way with the change to TimeSeriesDatabase.create()'s method signature from (self, metric, **options) to specifying the options explicitly, but I'm just going to ship as is. FYI, I'd like to hold off merging Ceres from the other branch until graphite-web supports reading past retentions which is something I've been working on getting put in |
Cherry-pick TimeSeriesDatabase from megacarbon branch
Merged in eeba611 |
I am on holidays so there is no rush on my side, yet. :-)
In megacarbon, there is a
I chose the quick path for now, with intent to properly address it later.
This is something I implemented in Ceres itself for now (I think you know this), I should rebase that PR for FYI purposes. Good to know that someone is working on pushing it out to the client though, that is definitely the right way to go about it. I'll raise a supplementary PR then which completes the |
It is becoming quite a pet peeve of mine to be stuck on the abandoned
megacarbon
branch and having to manually merge in upstream fixes. :-)While the
megacarbon
branch does a lot more, it is really only this part that is really relevant (to me), where all database actions are abstracted away, allowing any other database implementation to be plugged in.I've stopped short of duplicating
parseRetentionDefs
from whisper and adding aceres
backend. If there is no object against such things, I will push forward with those too. However what's been changed here is enough to allow a pause for review.