That's what I figured. I'm assuming the non-trivial way is to effectively replay all data into the new retention policy? Do you have a quick list of the breaking changes? If not, no worries, I'll go through the changelog.
On Tue, Aug 2, 2016 at 1:10 PM, Sean Beckett <[email protected]> wrote: > There is no trivial way to move data from one retention policy to another. A > `mv` command will just cause the index to lose track of the data files. I > would recommend upgrading to InfluxDB 0.9.6 at least, although there are > breaking changes between the releases. > > On Tue, Aug 2, 2016 at 8:37 AM, Steve V <[email protected]> wrote: >> >> I'm still running 0.9.2, and am running into an issue which looks like >> this https://github.com/influxdata/influxdb/issues/4634 Is there a way to >> create a new retention policy marked as the default, and move my existing >> data into it? Would a simple `mv` command do it? >> >> Thanks, >> Steve -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALQig88vzq%3Dex2Hbcmwv5tpC2iEe5D54e8dGSSYcX_K8jvOdWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
