Skip to content
This repository has been archived by the owner on Sep 2, 2020. It is now read-only.

allow choosing resolution by path regexp #1

Closed
pyr opened this issue Dec 9, 2013 · 6 comments · Fixed by #80
Closed

allow choosing resolution by path regexp #1

pyr opened this issue Dec 9, 2013 · 6 comments · Fixed by #80
Assignees
Milestone

Comments

@pyr
Copy link
Owner

pyr commented Dec 9, 2013

The configuration should allow specifying alternate rollup strategies based on path regexes

@ghost ghost assigned pyr Dec 9, 2013
@pyr pyr added the enhancement label Apr 3, 2014
@chjohnst
Copy link

From my understanding and looking at the code, it looks like cyanite only supports a single rollup value for all metric types?

@chjohnst
Copy link

chjohnst commented Oct 7, 2014

Is this something we can get implemented? Having a single rollup value is limiting cyanite usage to some extent, I have a small patch I did a few revisions back that worked but I ran into some issues where some the data was getting dropped. My clojure is not that good, hoping maybe you could take a stab it? This would allow me to move into production for some large data flows (over 500k messages/second).

@pyr
Copy link
Owner Author

pyr commented Oct 7, 2014

Yes, this definitely seems sensible

On Tue, Oct 7, 2014 at 10:12 PM, Christopher Johnston <
notifications@github.com> wrote:

Is this something we can get implemented? Having a single rollup value is
limiting cyanite usage to some extent, I have a small patch I did a few
revisions back that worked but I ran into some issues where some the data
was getting dropped. My clojure is not that good, hoping maybe you could
take a stab it? This would allow me to move into production for some large
data flows (over 500k messages/second).


Reply to this email directly or view it on GitHub
#1 (comment).

@pyr pyr mentioned this issue Jul 23, 2015
4 tasks
@pyr
Copy link
Owner Author

pyr commented Jul 23, 2015

@chjohnst I'm closing this now as #80 will mark the point at which this is fixed.

@pyr pyr closed this as completed Jul 23, 2015
@chjohnst
Copy link

Just looked at #80, will give it a go in my QA env. Did the schema change
though?
On Jul 23, 2015 9:24 AM, "Pierre-Yves Ritschard" notifications@github.com
wrote:

Closed #1 #1.


Reply to this email directly or view it on GitHub
#1 (comment).

@pyr
Copy link
Owner Author

pyr commented Jul 23, 2015

Hi @chjohnst,

Yes, the schema changed, the new schema addresses a number of issues with the original one.
My plans to address the transition are two-fold:

  • provide a cassandra-v1 store which will work with the old schema (not done yet)
  • provide a migration tool to be able to use cassandra-v2

@pyr pyr reopened this Jul 23, 2015
@pyr pyr closed this as completed Jul 23, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants