Hi, Since a year we put in production the Warp10 TTL and since a couple of month, a bot deletes our old inactive series. Since then, our production is very healthy and working well! Thanks for all those nice feature. I just have a mind a couple of small improvement that could be great for Warp10:
- Could we improve the DELETE method on the exec endpoint to take meta, quiesce/active as parameters? (I didn't find the time yet to contribute it) - At our scale, we do have issues with "deletall" calls as it can produces twice more traffic on a query more than the usual ingest/fetch ones. To reduce the impact, a new limit on the amount of time series than can be deleted in the same way that LIMIT or MAXGTS works, we have tested it in production. A native support on Warp10 of such limits could serves other Warp10 user. Let me know your plan on it, I can contribute as if my first implementation if you are interested. Best -- You received this message because you are subscribed to the Google Groups "Warp 10 users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/warp10-users/37006169-c19c-48cf-add3-421e6322c18bo%40googlegroups.com.
